View MVTX2603_1577045.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1 zarlink semiconductor inc. zarlink, zl and the zarlink semiconductor logo are trademarks of zarlink semiconductor inc. copyright 2003-2004, zarlink semiconductor inc. all rights reserved. features ? integrated single-chip 10/100/1000 mbps ethernet switch ? 24 10/100 mbps autosensing, fast ethernet ports with rmii or seri al interface (7ws) ? 2 gigabit ports with gmii, pcs, 10/100 and stacking (2 g per port) interface options per port ? serial interface for configuration ? supports two frame buffer memory domains with sram at 100 mhz ? supports memory size 2 mb, or 4 mb ? for 24+2, two sram domains (2 mb or 4 mb) are required. ? for 24+2 stacking (2 g per stacking port), two zbt domains (2 mb or 4 mb) are required. ? applies centralized shared memory architecture ? up to 64k mac addresses ? maximum throughput is 6.4 gbps non-blocking ? high performance packet forwarding (19.047 m packets per second) at full wire speed ? full duplex ethernet ieee 802.3x flow control ? backpressure flow control for half duplex ports ? supports ethernet multicasting and broadcasting and flooding control ? supports per-system option to enable flow control for best effort frames even on qos-enabled ports ? load sharing among trunked ports can be based on source mac and/or destination mac. the gigabit trunking group has one more option, based on source port. ? port mirroring to a dedicated port or port 23 ? built-in reset logic triggered by system malfunction ?i 2 c eeprom for configuration ? traffic classification ? 4 transmission priorities for fast ethernet ports with 2 dropping levels ? classification based on: - port based priority - vlan priority field in vlan tagged frame february 2004 ordering information MVTX2603ag 553 pin hsbga -40c to +85c MVTX2603 unmanaged 24-port 10/100 mb + 2-port 1 gb ethernet switch data sheet figure 1 - MVTX2603 system block diagram fdb interface frame data buffer a sram (1 m / 2 m) led search engine mct link frame engine fcb parallel/ serial management module 24 x 10 /100 rmii ports 0 - 23 vlan 1 mct frame data buffer b sram (1 m / 2 m) vlan 1 mct gmii/ port 24 pcs gmii/ port 25 pcs
MVTX2603 data sheet 2 zarlink semiconductor inc. - ds/tos field in ip packet - udp/tcp logical ports: 8 hard-wired and 8 programmable ports, including one programmable range ? the precedence of the above classifications is programmable ? qos support ? supports ieee 802.1p/q quality of service with 4 transmiss ion priority queues with delay bounded, strict priority, and wfq service disciplines ? provides 2 levels of dropping precedence with wred mechanism ? user controls the wred thresholds ? buffer management: per class and per port buffer reservations ? port-based priority: vlan priority in a tagged frame c an be overwritten by the prio rity of port vlan id. ? 3 port trunking groups, one for the 2 gigabit ports, and two groups for 10/100 ports, with up to 4 10/100 ports per group ? full set of led signals provided by a serial interface or 6 led signals dedicated to gigabit port status only (without serial interface) ? hardware auto-negotiation through serial management interface (mdio) for ethernet ports ? hardware auto-negotiation through serial management interface (mdio) for ethernet ports ? built-in self test for in ternal and external sram description the MVTX2603 is a high density, low cost, high performa nce, non-blocking ethernet switch chip. a single chip provides 24 ports at 10/100 mbps, 2 ports at 1000 mbps. the gigabit ports can also support 10/100 m and 2 g stacking modes. the chip supports up to 64 k mac addresses. the centra lized shared memory archit ecture permits a very high performance packet forwarding rate at up to 9.524 m packets per second at full wire speed. the chip is optimized to provide low-cost, high-performance workgroup switching. two frame buffer memory domains utilize cost-effecti ve, high-performance synchronous sram with aggregate bandwidth of 12.8 gbps to support full wire speed on all ports simultaneously. in the 24+2 stacking (2 g per stacking port) configuration, 2 zbt domains are needed. with delay bounded, strict priority, and/or wfq transmission scheduling and wred dropping schemes, the MVTX2603 provides powerful qos functions for various multimedia and mission-critical applications. the chip provides 4 transmission priorities (8 priorities per gigabit port) and 2 levels of dropping precedence. each packet is assigned a transmission priority and dropping precedence based on the vlan priority field in a vlan tagged frame, or the ds/tos field, or the udp/tcp logical port fi elds in ip packets. the MVTX2603 recognizes a total of 16 udp/tcp logical ports, 8 hard-wired and 8 programmable (including one programmable range). the MVTX2603 supports 3 groups of port trunking/load sharing. one group is dedicated to the two gigabit ports and the other two groups to 10/100 ports, where each 10/100 group can contain up to 4 ports. port trunking/load sharing can be used to group ports between interlinked sw itches to increase the effective network bandwidth. in half-duplex mode, all ports support backpressure flow c ontrol, to minimize the risk of losing data during long activity bursts. in full-duplex mode, ieee 802.3x flow control is provided. the mv tx2603 also supports a per- system option to enable flow control for best effort fram es even on qos-enabled ports. the physical coding sublayer (pcs) is integrated on-chip to provide a direct 10-bit interface for connection to serdes chips. the pcs can be bypassed to provide a gmii interface. the MVTX2603 is fabricated using 0.25 micron technology. inputs, however, are 3.3 v tolerant, and the outputs are capable of directly interfacing to lvttl levels. the MVTX2603 is packaged in a 553-pin ball grid array package.
MVTX2603 data sheet table of contents 3 zarlink semiconductor inc. 1.0 block functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.1 frame data buffer (fdb) interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.2 gmii/pcs mac module (gmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.3 physical coding sublayer (pci) interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.4 10/100 mac module (rmac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.5 configuration interface module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.6 frame engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.7 search engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.8 led interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.9 internal memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.0 system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.1 configuration mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2 i2c interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.2.1 start condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.2 address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.3 data direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.4 acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.5 data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2.6 stop condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3 synchronous serial interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.3.1 write command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.3.2 read command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.4 stacking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.0 MVTX2603 data forwarding protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.1 unicast data frame forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 3.2 multicast data frame forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4.0 memory interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.1 overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.2 zbt support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.3 detailed memory information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4 memory requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.0 search engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.1 search engine overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5.2 basic flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3 search, learning, and aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3.1 mac search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3.2 learning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3.3 aging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.4 quality of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.5 priority classification rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 5.6 port based vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 5.7 memory configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 6.0 frame engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.1 data forwarding summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2 frame engine details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2.1 fcb manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2.2 rx interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2.3 rxdma. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.2.4 txq manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 6.3 port control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 6.4 txdma. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
MVTX2603 data sheet table of contents 4 zarlink semiconductor inc. 7.0 quality of service and flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.1 model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 7.2 four qos configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 7.3 delay bound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 7.4 strict priority and best effort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.5 weighted fair queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.6 shaper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 7.7 wred drop threshold management suppor t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.8 buffer management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 7.8.1 dropping when buffers are scarce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.9 MVTX2603 flow control basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.9.1 unicast flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.9.2 multicast flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 7.10 mapping to ietf diffserv classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 8.0 port trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.1 features and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.2 unicast packet forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.3 multicast packet forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 8.4 trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 9.0 port mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 9.1 port mirroring features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 9.2 setting registers for port mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 10.0 tbi interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 11.0 gpsi (7ws) interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 11.1 gpsi connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 11.2 scan link and scan col interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 12.0 led interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 12.1 led interface introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 12.2 port status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 12.3 led interface timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 13.0 register definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 13.1 MVTX2603 register description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 13.2 group 0 address mac ports group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 13.2.1 ecr1pn: port n control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 13.2.2 ecr2pn: port n control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 13.2.3 ggcontrol ? extra giga port control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 13.3 group 1 address vlan group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 13.3.1 avtcl ? vlan type code register low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 13.3.2 avtch ? vlan type code register high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 13.3.3 pvmap00_0 ? port 00 configuration register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4 13.3.4 pvmap00_1 ? port 00 configuration register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 13.3.5 pvmap00_2 ? port 00 configuration register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 13.3.6 pvmap00_3 ? port 00 configuration register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 13.4 port configuration register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 13.4.1 pvmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 13.4.2 trunk0_mode? trunk group 0 mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 13.4.3 trunk1_mode ? trunk group 1 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 13.5 group 4 address search engine group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 13.5.1 tx_age ? tx queue aging timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 13.5.2 agetime_low ? mac address aging time low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 13.5.3 agetime_high ?mac addr ess aging time high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
MVTX2603 data sheet table of contents 5 zarlink semiconductor inc. 13.5.4 se_opmode ? search engi ne operation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 13.6 group 5 address buffer control/qos group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.6.1 fcbat ? fcb aging timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.6.2 qosc ? qos control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.6.3 fcr ? flooding control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 13.6.4 avpml ? vlan priority map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 13.6.5 avpmm ? vlan priority ma p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 13.6.6 avpmh ? vlan priority map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 13.6.7 tospml ? tos priority map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 13.6.8 tospmm ? tos priority map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 13.6.9 tospmh ? tos priority map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 13.6.10 avdm ? vlan discard map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 13.6.11 tosdml ? tos discard map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 13.6.12 bmrc - broadcast/multicast rate control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 13.6.13 ucc ? unicast congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 13.6.14 mcc ? multicast congestion control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 13.6.15 pr100 ? port reservation for 10/100 ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 13.6.16 prg ? port reservation for giga port s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 13.6.17 sfcb ? share fcb size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 13.6.18 c2rs ? class 2 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 13.6.19 c3rs ? class 3 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13.6.20 c4rs ? class 4 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13.6.21 c5rs ? class 5 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13.6.22 c6rs ? class 6 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13.6.23 c7rs ? class 7 reserve size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 13.6.24 classes byte limit set 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 13.6.25 classes byte limit set 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 13.6.26 classes byte limit set 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 13.6.27 classes byte limit set 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 13.6.28 classes byte limit giga port 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 13.6.29 classes byte limit giga port 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 13.6.30 classes wfq credit set 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 13.6.31 classes wfq credit set 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 13.6.32 classes wfq credit set 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 13.6.33 classes wfq credit set 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 13.6.34 classes wfq credit port g1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 13.6.35 classes wfq credit port g2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 13.6.36 class 6 shaper control port g1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 13.6.37 class 6 shaper control port g2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 13.6.38 rdrc0 ? wred rate control 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 13.6.39 rdrc1 ? wred rate control 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 13.6.40 user defined logical ports and well known ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 13.6.40.1 user_port0_(0~7) ? user define logical port (0 ~7). . . . . . . . . . . . . . . . . . . . . . . . . . . 62 13.6.40.2 user_port_[1:0]_priority - user define logic port 1 and 0 pr iority . . . . . . . . . . . . . 63 13.6.40.3 user_port_[3:2]_priority - user define logic port 3 and 2 pr iority . . . . . . . . . . . . . 63 13.6.40.4 user_port_[5:4]_priority - user define logic port 5 and 4 pr iority . . . . . . . . . . . . . 63 13.6.40.5 user_port_[7:6]_priority - user define logic port 7 and 6 pr iority . . . . . . . . . . . . . 63 13.6.40.6 user_port_enable [7:0] ? user define logic 7 to 0 port enables . . . . . . . . . . . . . . . 63 13.6.40.7 well_known_port [1:0] priority- well k nown logic port 1 and 0 priority . . . . . . 64 13.6.40.8 well_known_port [3:2] priority- well k nown logic port 3 and 2 priority . . . . . . 64 13.6.40.9 well_known_port [5:4] priority- well k nown logic port 5 and 4 priority . . . . . . 64 13.6.40.10 well_known_port [7:6] priority- well known logic port 7 and 6 priority . . . . . 64
MVTX2603 data sheet table of contents 6 zarlink semiconductor inc. 13.6.40.11 well known_port_enable [7:0] ? well known logic 7 to 0 port enables. . . . . . . 65 13.6.40.12 rlowl ? user define range lo w bit 7:0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.6.40.13 rlowh ? user define range lo w bit 15:8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.6.40.14 rhighl ? user define range high bit 7:0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.6.40.15 rhighh ? user define range high bit 15:8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.6.40.16 rpriority ? user define range priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 13.7 group 6 address misc group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 13.7.1 mii_op0 ? mii register option 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 13.7.2 mii_op1 ? mii register option 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 13.7.3 fen ? feature register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 13.7.4 miic0 ? mii co mmand register 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 13.7.5 miic1 ? mii co mmand register 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 13.7.6 miic2 ? mii co mmand register 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 13.7.7 miic3 ? mii co mmand register 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 13.7.8 miid0 ? mii data re gister 0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 13.7.9 miid1 ? mii data re gister 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 13.7.10 led mode ? led control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 13.7.11 checksum - eeprom checksum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 9 13.8 group 7 address port mirroring group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 13.8.1 mirror1_src ? port mirror source port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 13.8.2 mirror1_dest ? port mirror destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 13.8.3 mirror2_src ? port mirror source port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 13.8.4 mirror2_dest ? port mirror destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 13.9 group f address cpu access group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 13.9.1 gcr-global control register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 13.9.2 dcr-device status and signature register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71 13.9.3 dcr1-giga port status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 13.9.4 dpst ? device port stat us register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 13.9.5 dtst ? data read back register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 13.9.6 pllcr - pll control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 13.9.7 lclk - la_clk delay from internal oe_clk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 13.9.8 oeclk - internal oe_clk delay from sclk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3 13.9.9 da ? da register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13.10 tbi registers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13.10.1 control register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 13.10.2 status register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 13.10.3 advertisement register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 13.10.4 link partner ability register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 13.10.5 expansion register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 13.10.6 extended status register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 14.0 bga and ball signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 14.1 bga views (top-view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 14.1.1 encapsulated view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 14.2 ball ? signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 14.2.1 ball signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 14.3 ball ? signal name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 14.4 ac/dc timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 14.4.1 absolute maxi mum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 14.4.2 dc electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 14.4.3 recommended operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 14.4.4 typical reset & bootstrap timing di agram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 14.5 local frame buffer sbram memory inte rface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
MVTX2603 data sheet table of contents 7 zarlink semiconductor inc. 14.5.1 local sbram memory interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 14.6 local switch database sbram memory interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 14.6.1 local sbram memory interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 14.7 ac characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 14.7.1 reduced media independent interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 14.7.2 gigabit media independent interface - port a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 14.7.3 ten bit interface - port a . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 14.7.4 gigabit media independent interface - port b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 14.7.5 ten bit interface - port b . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 14.7.6 led interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 14.7.7 scanlink scancol output delay timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 14.7.8 mdio input setup and hold timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 14.7.9 i 2 c input setup timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 14.7.10 serial interface setup timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
MVTX2603 data sheet list of figures 8 zarlink semiconductor inc. figure 1 - MVTX2603 system block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 figure 2 - data transfer format for i2c interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 3 - write command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 4 - read command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 5 - MVTX2603 sram interface block diagram (dmas for 10/1000 ports only) . . . . . . . . . . . . . . . . . . . . 15 figure 6 - memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 figure 7 - priority classification rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 figure 8 - memory configuration for: 2 banks, 1 layer, 2 mb tota l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 figure 9 - memory configuration for: 2 banks, 2 layer, 4 mb tota l . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 figure 10 - memory configuration for: 2 banks, 1 layer, 4 mb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 figure 11 - memory configuration for: 2 banks, 2 layers, 4 mb total . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 12 - memory configuration for: 2 banks, 1 layer, 4 mb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 13 - buffer partition scheme used to implement mvtx 2603 buffer management . . . . . . . . . . . . . . . . . . 30 figure 14 - tbi connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 figure 15 - gpsi (7ws) mode connection diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 figure 16 - scan link and scan collison status diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 figure 17 - timing diagram of led interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 figure 18 - typical reset & bootstrap timing diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 figure 19 - local memory interface ? input setup and hold timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 figure 20 - local memory interface - output valid delay timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 figure 21 - local memory interface ? input setup and hold timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 figure 22 - local memory interface - output valid delay timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 figure 23 - ac characteristics ? reduced media independent interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 figure 24 - ac characteristics ? reduced media independent interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 figure 25 - ac characteristics- gmii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 figure 26 - ac characteristics ? gigabit media independent interf ace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 figure 27 - gigabit tbi interface transmit timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 figure 28 - gigabit tbi interface receive timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 figure 29 - ac characteristics- gmii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 figure 30 - ac characteristics ? gigabit media independent interf ace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 figure 31 - gigabit tbi interface transmit timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 figure 32 - gigabit tbi interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 figure 33 - ac characteristics ? led interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 figure 34 - scanlink scancol output delay timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 figure 35 - scanlink, scancol setup timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 figure 36 - mdio input setup and hold timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 figure 37 - mdio output delay timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 figure 38 - i2c input setup timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 figure 39 - i2c output delay timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 figure 40 - serial interface setu p timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 figure 41 - serial interface output delay timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
MVTX2603 data sheet list of tables 9 zarlink semiconductor inc. table 1 - memory configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 2 - pvmap register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 3 - supported memory configurations (pipeline sbram mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 4 - supported memory configurations (zbt mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 5 - options for memory configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 6 - two-dimensional world traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 8 - four qos configurations for a gigabit port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 7 - four qos configurations for a 10/100 mbps port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 9 - wred drop thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 table 10 - mapping between MVTX2603 and ietf diffserv classes fo r gigabit ports . . . . . . . . . . . . . . . . . . . . . 32 table 11 - mapping between MVTX2603 and ietf diffserv classes for 10/100 ports . . . . . . . . . . . . . . . . . . . . . 32 table 12 - MVTX2603 features enabling ietf diffserv standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 table 13 - reset & bootstrap timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 table 14 - ac characteristics ? local frame buffer sbram memory interface . . . . . . . . . . . . . . . . . . . . . . . . . . 96 table 15 - ac characteristics ? local swit ch database sbram memory in terface . . . . . . . . . . . . . . . . . . . . . . . 98 table 16 - ac characteristics ? reduced media independent interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 table 17 - ac characteristics ? gigabit media independent interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 table 18 - output delay timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 table 19 - input setup timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 table 20 - ac characteristics ? gigabit media independent interf ace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 table 21 - output delay timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 table 22 - input setup timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 table 23 - ac characteristics ? led interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 table 24 - scanlink, scancol timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 table 25 - mdio timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 table 26 - i2c timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 table 27 - serial interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
MVTX2603 data sheet 10 zarlink semiconductor inc. 1.0 blo ck functionality 1.1 frame data buffer (fdb) interfaces the fdb interface supports pipelined synchronrous burst sram (sbram) memory at 100 mhz. to ensure a non- blocking switch, two memory domains are required. each domain has a 64 bit wide memory bus. at 100 mhz, the aggregate memory bandwidth is 12.8 gbps, which is enough to support 24 10/100 mbps and 2 gigabit ports at full wire speed switching. for 24+ 2 stacking applic ation, zbt memory at 125 mhz is required. the switching database is also located in the external sbram; it is used for storing mac addresses and their physical port number. it is duplicated and stored in both memory domains. therefore, when the system updates the contents of the switching database, it has to wr ite the entry to both domains at the same time. 1.2 gmii/pcs mac module (gmac) the gmii/pcs media access control (mac) module provides the necessary buffers and control interface between the frame engine (fe) and the external physical device (phy). the MVTX2603 gmac implements both gmii and mii interfaces, which offers a simple migration from 10/100 to 1 g. the gmac of the MVTX2603 meets the ieee 802.3z specificat ion. it is able to oper ate in 10 m/100 m either half or full duplex mode with a back pressure/flow control mechanism or in 1 g full duplex mode with flow control mechanism. furthermore, it will automatically retransmit upon collision for up to 16 total transmissions. phy addresses for gmac are 01h and 02h. 1.3 physical coding sublayer (pci) interface for the MVTX2603, the 1000base-x pci inte rface is designed interna lly and may be utilized in the absence of a gmii. the pcs incorporates all the functions required by the gmii to include encoding (decoding) 8b gmii data to (from) 8b/10b tbi format for phy commu nication and generating collision detect (col) signals for half-duplex mode. it also manages the auto negotiation process by in forming the management entity that the phy is ready for communications. the on-chip tbi may be disabled if tbi exists within the gigabit phy. the tbi interface provides a uniform interface for all 1000 mbps phy implementations. the pcs comprises the pcs transmit, synchronization, pcs receive and auto negotiation processes for 1000base-x. the pcs transmit process sends the tbi signals txd [9:0] to the physi cal medium and generates the gmii collision detect (col) signal based on whether a reception is occurring simultaneously with transmission. additionally, the transmit process generates an internal ?transmitting? flag and monitors auto negotiation to determine whether to transmit data or to reconfigure the link. the pcs synchronization process determines whether or not the receive channel is operational. the pcs receive process generates rxd [7:0] on the gmii fr om the tbi data [9:0], and th e internal ?receiving? flag for use by the transmit processes. the pcs auto negotiation process allows the MVTX2603 to exchange configuration information between two devices that share a link segment and to automatically conf igure the link for the approp riate speed of operation for both devices. 1.4 10/100 mac module (rmac) the 10/100 media access control module provides the ne cessary buffers and control interface between the frame engine (fe) and the external physical device (phy). the MVTX2603 has two interfaces, rmii or serial (only for 10 m). the 10/100 mac of the MVTX2603 device meets the ieee 802.3 specification. it is able to operate in either half or full duplex mode with a back pressure/flow contro l mechanism. in addition, it will automatically retransmit upon collision for up to 16 total transmissions. the phy address for 24 10/100 mac are from 08h to 1fh.
MVTX2603 data sheet 11 zarlink semiconductor inc. 1.5 configuration interface module the MVTX2603 supports a serial and an i 2 c interface, whic h provides an easy way to configure the system. once configured, the resulting configuration can be stored in an i 2 c eeprom. 1.6 frame engine the main function of the frame engine is to forward a fram e to its proper destination po rt or ports. when a frame arrives, the frame engine parses the frame header (64 by tes) and formulates a switching request, which is sent to the search engine to resolve the destination port. the arri ving frame is moved to the fdb. after receiving a switch response from the search engine, the frame engine perf orms transmission scheduling based on the frame?s priority. the frame engine forwards the frame to the mac module when the frame is ready to be sent. 1.7 search engine the search engine resolves the frame?s destination port or ports according to the destination mac address (l2). it also performs mac learning, priority assignment and trunking functions. 1.8 led interface the led interface provides a serial interface for carrying 24 +2 port status signals. it can also provide direct status pins (6) for the two gigabit ports. 1.9 internal memory several internal tables are required and are described as follows: ? frame control block (fcb) - each fcb entry contains the control information of the associated frame stored in the fdb, e.g., frame size, read/write pointer, transmission priority, etc. ? mct link table - the mct link table stores the linked list of mct entries that have collisions in the external mac table. the external mac table is located in the fdb memory. note: the external mac table is located in the external sbram memory. 2.0 system configuration 2.1 configuration mode the MVTX2603 can be configured by eeprom (24c02 or compatible) via an i 2 c interface at boot time, or via a synchronous serial interface during operation. 2.2 i 2 c interface the i 2 c interface uses two bus lines, a serial data line (sda) and a serial clock line (scl). the scl line carries the control signals that facilitate the transfe r of information from eeprom to the switch. data transf er is 8-bit serial and bidirectional, at 50 kbps. data transfer is perfo rmed between master and slave ic using a request / acknowledgment style of protocol. the master ic genera tes the timing signals and terminates data transfer. figure 2 depicts the data transfer format. figure 2 - data transfer format for i 2 c interface start slave address r/w ack data 1 (8 bits) ack data 2 ack data m ack stop
MVTX2603 data sheet 12 zarlink semiconductor inc. 2.2.1 start condition generated by the master (in our case, the MVTX2603). the bus is considered to be busy after the start condition is generated. the start condition occurs if while the scl line is high, there is a high-to-low transition of the sda line. other than in the start condition (and stop condition), the data on the sda line must be stable during the high period of scl. the high or low state of sda can only change when scl is low. in addition, when the i 2 c bus is free, both lines are high. 2.2.2 address the first byte after the start condition determines which sl ave the master will select. th e slave in our case is the eeprom. the first seven bits of the first data byte ma ke up the slave address. 2.2.3 data direction the eighth bit in the first byte after the start conditi on determines the direction (r /w) of the message. a master transmitter sets this bit to w; a master receiver sets this bit to r. 2.2.4 acknowledgment like all clock pulses, the acknowledgment-related clock pul se is generated by the master. however, the transmitter releases the sda line (high) during the acknowledgment cl ock pulse. furthermore, the receiver must pull down the sda line during the acknowledge pulse so that it remains stable low during the high period of this clock pulse. an acknowledgment pulse follows every byte transfer. if a slave receiver does not acknowledge after any byte, t hen the master generates a stop condition and aborts the transfer. if a master receiver does not acknowledge after any byte , then the slave transmitter must release the sda line to let the master generate the stop condition. 2.2.5 data after the first byte containing the address, all bytes that follow are data bytes. each byte must be followed by an acknowledge bit. data is transferred msb first. 2.2.6 stop condition generated by the master. the bus is cons idered to be free after the stop condition is generated. the stop condition occurs if while the scl line is high, there is a low-to-high transition of the sda line. the i 2 c interface serves the function of configuring the mvtx 2603 at boot time. the master is the MVTX2603 and the slave is the eeprom memory. 2.3 synchronous serial interface the synchronous serial interface serves the function of configuring the MVTX2603 not at boot time but via a pc. the pc serves as master and the MVTX2603 serves as slav e. the protocol for the synchronous serial interface is nearly identical to the i 2 c protocol. the main difference is that there is no acknowledgment bit after each byte of data transferred. the unmanaged MVTX2603 uses a synchronous serial interf ace to program the internal registers. to reduce the number of signals required, the register address, command and data are shifted in serially through the d0 pin. strobe- pin is used as the shift clock. autofd- pin is used as data return path.
MVTX2603 data sheet 13 zarlink semiconductor inc. each command consists of four parts. start pulse register address read or write command data to be written or read back any command can be aborted in the middle by sending a abort pulse to the MVTX2603. a start command is detected when d0 is sampled high when strobe- rise and d0 is sampled low when strobe- fall. an abort command is detected when d0 is sampled low when strobe- rise and d0 is sampled high when strobe- fall. 2.3.1 write command figure 3 - write command 2.3.2 read command figure 4 - read command all registers in MVTX2603 can be modified through this synchronous serial interface. 2.4 stacking the two gigabits ports can be used as link between boxes. each gigabit port can be accelerated to 2 gpbs if desired (in conjunction with zbt memory domains at 125 mhz ). if both gigabit ports are used for this purpose, this provides a total of 4 gbps of bandwidth between devices. strobe- d0 a0 a2 ... a9 a10 a11 a1 w d0 d1 d2 d3 d4 d5 d6 d7 start address command data 2 extra clocks after last transfer a0 a1 a2 a9 a10 a11 ... w d0 d1 d2 d3 d4 d5 d6 d7 2 extra clock cycles after last transfer strobe- d0 autofd- a0 a1 a2 ... a9 a10 a11 r d0 d1 d2 d3 d4 d5 d6 d7 start address command data a0 a1 a2 a9 a10 a11 ... r d0 d1 d2 d3 d4 d5 d6 d7
MVTX2603 data sheet 14 zarlink semiconductor inc. 3.0 MVTX2603 data forwarding protocol 3.1 unicast data frame forwarding when a frame arrives, it is assigned a handle in memo ry by the frame control buffer manager (fcb manager). an fcb handle will always be available, because of advance buffer reservations. the memory (sram) interface consists of two 64-bit buses, connected to two sram banks, a and b. the receive dma (rxdma) is responsible for multiplexing the data and the address. on a port?s ?turn,? the rxdma will move 8 bytes (or up to the end-of-frame) from the port?s associ ated rxfifo into memory (fra me data buffer, or fdb). once an entire frame has been moved to the fdb and a good end-of-frame (eof) has been received, the rx interface makes a switch request. the rxdma arbitrates among multiple switch requests. the switch request consists of the first 64 bytes of a frame, containing among other things, the source and destination mac addresses of the frame. the search engi ne places a switch response in the switch response queue of the frame engine when done. among other in formation, the search engine will have resolved the destination port of the frame and will have determined that the frame is unicast. after processing the switch response, the transmission queue manager (txq manager) of the frame engine is responsible for notifying the destination port that it has a frame to forward to it. bu t first, the txq manager has to decide whether or not to drop the frame, based on globa l fdb reservations and usage, as well as txq occupancy at the destination. if the frame is not dropped, then the txq manager links the frame?s fcb to the correct per-port- per-class txq. unicast txq?s are linked lists of transmi ssion jobs, represented by their associated frames? fcb?s. there is one linked list for each transmission class for eac h port. there are 4 transmission classes for each of the 24 10/100 ports and 8 classes for each of the two gigabit ports ? a total of 112 unicast queues. the txq manager is responsible for scheduling transmission among the queues representing different classes for a port. when the port control module determines that ther e is room in the mac transmission fifo (txfifo) for another frame, it requests the handle of a new frame from the txq manager. the txq manager chooses among the head-of-line (hol) frames from the per-class queues for that port using a zarlink semiconductor scheduling algorithm. the transmission dma (txdma) is responsible for multiplexing the data and the address. on a port?s turn, the txdma will move 8 bytes (or up to the eof) from memory into the port?s associated txfifo. after reading the eof, the port control requests a fcb release for that frame. the txdma arbitrates among multiple buffer release requests. the frame is transmitted from the txfifo to the line. 3.2 multicast data frame forwarding after receiving the switch re sponse, the txq manager has to make the dropping decision. a global decision to drop can be made, based on global fdb utilization and reservat ions. if so, then the fcb is released and the frame is dropped. in addition, a selective decision to drop can be made, based on the txq occupancy at some subset of the multicast packet?s destinations. if so, then the frame is dropped at some destinations but not others and the fcb is not released. if the frame is not dropped at a particular destination po rt, then the txq manager formats an entry in the multicast queue for that port and class. multicast queues are physi cal queues (unlike the linked lists for unicast frames). there are 2 multicast queues for each of the 24 10/100 ports. the queue with higher priority has room for 32 entries and the queue with lower priority has room for 64 entries. there are 4 multicast queues for each of the two gigabit ports. the sizes of the queues are: 32 entries (higher prio rity queue, 32 entries, 32 entries and 64 entries (lower priority queue). there is one multicast queue for every two priority classes. for the 10/100 ports to map the 8 transmit priorities into 2 multicast queues, the 2 lsb are discarded. for the gigabit ports to map the 8 transmit priorities into 4 multicast queues, the lsb are discarded.
MVTX2603 data sheet 15 zarlink semiconductor inc. during scheduling, the txq manager treats the unicast qu eue and the multicast queue of the same class as one logical queue. the older head of line of the two queues is forwarded first. the port control requests a fcb release only after the eo f for the multicast frame has been read by all ports to which the frame is destined. 4.0 memory interface 4.1 overview the MVTX2603 provides two 64-bit wide sram banks, sram bank a and sram bank b, with a 64-bit bus connected to each. each dma can read and write from both bank a and bank b. the following figure provides an overview of the MVTX2603 sram banks. figure 5 - MVTX2603 sram interface block diagram (dmas for 10/1000 ports only) 4.2 zbt support the MVTX2603 supports zero bus turnaround (zbt). zbt is a synchronous sram architecture that is optimized for networking and telecommunications applications. it can significantly increase the switch?s internal bandwidth when compared to standard pipeline syncburst sram. the zbt architecture is optimized for switching and other applications with highly random reads and writes. zbt srams eliminate all idle cycles when turning the data bus around from a writ e operation to a read operation (or vice versa). th is feature results in dramatic performanc e improvements in systems that have such traffic patterns (that is, frequent and random read and write access to the sram). please refer to the zbt applic ation note for further details. 4.3 detailed memory information because the bus for each bank is 64-bits wide, frames ar e broken into 8-byte granules, written to and read from memory. the first 8-byte granule gets written to bank a, the second 8-byte granule gets written to bank b, and so on in alternating fashion. when reading frames from memo ry, the same procedure is followed, first from a, then from b and so on. sram bank a txdma 0-7 txdma 8-15 txdma 16-23 rxdma 0-7 rxdma 8-15 rxdma 16-23 sram bank b
MVTX2603 data sheet 16 zarlink semiconductor inc. the reading and writing from alternating memory ba nks can be performed with minimal waste of memory bandwidth. what?s the worst case? for any speed port, in the worst case, a 1-byte-long eof granule gets written to bank a. this means that a 7-byte segment of bank a bandwidth is idle, and furthermore, the next 8-byte segment of bank b bandwidth is idle, because the first 8 bytes of the next frame will be written to bank a, not b. this scenario results in a maximum 15 bytes of wast e per frame, which is always acceptable because the interframe gap is 20 bytes. search engine data is written to both banks in parallel. in this way, a search engine read operation can be performed by either bank at any time without a problem. 4.4 memory requirements to speed up searching and decrease memory latency, the external mct database is duplicated in both memory banks. to support 64 k mct, 4 mb memory is required. up to 2 k frame buffers are supported and they will use 3 mb of memory. the maximum system memory requirement is 4 mb. if less memory is desired, the configuration can scale down proportionally. figure 6 - memory map 5.0 search engine 5.1 search engine overview the MVTX2603 search engine is optimized for high throughput searching, with enhanced features to support: ? up to 64 k mac addresses ? 3 groups of port trunking (1 for the two gigabit ports, and 2 others) ? traffic classification into 4 (o r 8 for gigabit) transmission priorities, and 2 drop precedence levels ? flooding, broadcast, multicast storm control ? mac address learning and aging ? port based vlan bank a bank b frame buffer max mac address 1m 1m 1k 32k 2m 2m 2k 64k table 1 - memory configuration 1 m bank a 1 m bank b 2 m bank a 2 m bank b 0.75 m 0.75 m 1.5 m 1.5 m 0.25 m 0.25 m 0.5 m 0.5 m frame data buffer (fdr) area mac address control table (mct) area
MVTX2603 data sheet 17 zarlink semiconductor inc. 5.2 basic flow shortly after a frame enters the MVTX2603 and is writt en to the frame data buffer (fdb), the frame engine generates a switch request, which is sent to the search en gine. the switch request consists of the first 64 bytes of the frame, which contain all the necessary information fo r the search engine to perfo rm its task. when the search engine is done, it writes to the switch response queue, and the frame engine uses the information provided in that queue for scheduling and forwarding. in performing its task, the search engine extracts and compresses the useful information from the 64-byte switch request. among the information extracted are the source and destination mac addresses, the transmission and discard priorities, whether the frame is unicast or multicas t. requests are sent to the external sram to locate the associated entries in the external hash table. when all the information has been collected from external sram, the search engine has to compare the mac address on the current entry with the mac address for which it is searching. if it is not a match, the process is repeated on the internal mct table. all mct entries other than the first of each linked list are maintained internal to the chip. if the desired mac address is still not found, t hen the result is either learning (source mac address unknown) or flooding (destination mac address unknown). in addition, port based vlan information is used to sele ct the correct set of destination ports for the frame (for multicast) or to verify that the frame?s destination port is associ ated with the vlan (for unicast). if the destination mac address belongs to a port trunk, then the trunk number is retrieved instead of the port number. but on which port of the trunk will the frame be transmitted? this is easily computed using a hash of the source and destination mac addresses. as stated earlier, when all th e information is comp iled the switch resp onse is generated. 5.3 search, learning, and aging 5.3.1 mac search the search block performs source mac address and dest ination mac address searching. as we indicated earlier, if a match is not found, then the next entry in the linked list must be examined, and so on until a match is found or the end of the list is reached. the port based vlan bitmap is used to determine whether the frame should be forwarded to the outgoing port. when the egress port is not included in the ingress port vlan bitmap, the packet is discarded. the mac search block is also responsible for updating the source mac address timestamp and the vlan port association timestamp, used for aging. 5.3.2 learning the learning module learns new mac addresses and per forms port change operations on the mct database. the goal of learning is to update this database as the networking environment changes over time. learning and port change will be performed based on memory slot availability only. 5.3.3 aging aging time is controlled by register 400h and 401h. the aging module scans and ages mct entries based on a programmable ?age out? time interval. as we indicated earlier, the search module updates the source mac address timestamps for each frame it processes. when an entry is ready to be aged, the entry is removed from the table.
MVTX2603 data sheet 18 zarlink semiconductor inc. 5.4 quality of service quality of service (qos) refers to the ability of a network to provide bett er service to selected network traffic over various technologies. primary goals of qos include dedicated bandwidth, controlled jitter and latency (required by some real-time and interactive traffic) and improved loss characteristics. traditional ethernet networks have had no prioritization of tr affic. without a protocol to prioritize or differentiate traffic, a service level known as ?best effort? attempts to get all the packets to their intended destinations with minimum delay; however, there are no guarantees. in a congested network or when a low-performance switch/router is overloaded, ?best effort? becomes unsuitable for delay-sensitive traffic and mission-critical data transmission. the advent of qos for packet-based systems accommodates the integratio n of delay-sensitive video and multimedia traffic onto any existing ethernet network. it al so alleviates the congestion issues that have previously plagued such ?best effort? ne tworking systems. qos provides ethernet networks with the break through technology to prioritize traffic and ensure th at a certain transmission will have a guaranteed minimum amount of bandwidth. extensive core qos mechanisms are built into the MVTX2603 architecture to ensure policy enforcement and buffering of the ingress port, as well as weighted fair-queue (wfq) scheduling at the egress port. in the MVTX2603, qos-based policies sort traffic into a small number of classes and mark the packets accordingly. the qos identifier provides specific treatment to traffic in different classes, so that different quality of service is provided to each class. frame and packet scheduling and discarding policies are determined by the class to which the frames and packets belong. for example, the overall se rvice given to frames and packets in the premium class will be better than that given to the standard class; the premium class is expected to experience lower loss rate or delay. the MVTX2603 supports the following qos techniques: ? in a port-based setup, any station connected to the same physical port of the switch will have the same transmit priority. ? in a tag-based setup, a 3-bit field in the vlan tag provides the priority of the packet. this priority can be mapped to different queues in the switch to provide qos. ? in a tos/ds-based set up, tos stands for ?type of service? that may include ?minimize delay,? ?maximize throughput,? or ?maximize reliability.? network nodes may select routing paths or forwarding behaviours that are suitably engineered to satisfy the service request. ? in a logical port-based set up, a logical port provides the application information of the packet. certain applications are more sensitive to delays than others; using logical ports to classify packets can help speed up delay sensitive applications, such as voip. 5.5 priority classification rule figure 7 on page 19 shows the MVTX2603 priority classification rule
MVTX2603 data sheet 19 zarlink semiconductor inc. figure 7 - priority classification rule 5.6 port based vlan an administrator can use the pvmap registers to configure the MVTX2603 for port-based vlan. for example, ports 1-3 might be assigned to the marketing vlan, ports 4-6 to the engineering vlan, and ports 7-9 to the administrative vlan. the MVTX2603 determines the vlan membership of each packet by noting the port on which it arrives. from there, the MVTX2603 determines which outgoing port(s) is/are eligible to transmit each packet, or whether the packet should be discarded. table 2 - pvmap register for example, in the above table, a 1 denotes that an outgoing port is eligible to receive a packet from an incoming port. a 0 (zero) denotes that an outgoing port is not elig ible to receive a packet from an incoming port. destination port numbers bit map port registers 26 ? 2 1 0 register for port #0 pvmap00_0[7:0] to pvmap00_3[2:0] 0110 register for port #1 pvmap01_0[7:0] to pvmap01_3[2:0] 0101 register for port #2 pvmap02_0[7:0] to pvmap02_3[2:0] 0000 ? register for port #26 pvmap26_0[7:0] to pvmap26_3[2:0] 0000 fix port priority ? yes yes yes yes yes yes no no no no no use tos use logical port use default port settings use vlan priority use default port settings tos precedence over vlan? vlan tag ? ip frame ? ip (fcr register, bit 7) no use logical port
MVTX2603 data sheet 20 zarlink semiconductor inc. in this example: ? data packets received at port #0 are eligible to be sent to outgoing ports 1 and 2 ? data packets received at port #1 are eligible to be sent to outgoing ports 0, and 2 ? data packets received at port #2 are not eligible to be sent to ports 0 and 1 5.7 memory configurations the MVTX2603 supports the following memory configurat ions. sbram modes support 1 m and 2 m configurations, while zbt mode supports 4 m configurations, 2 m per do main (bank). for detail connection information, please reference the memory application note. table 3 - supported memory confi gurations (pipeline sbram mode) configuration 1 m per bank (bootstrap pin tstout7 = open) 2 m per bank (bootstrap pin tstout7 = pull down) connections single layer (bootstrap pin tstout13 = open) two 128 k x 32 sram/bank or one 128 k x 64 sram/bank two 256 k x 32 sram/bank connect 0e# and we# double layer (bootstrap pin tstout13 = pull down) na four 128 k x 32 sram/bank or two 128 k x 64 sram/bank connect 0e0# and we0# connect 0e1# and we1#
MVTX2603 data sheet 21 zarlink semiconductor inc. table 4 - supported memory configurations (zbt mode) table 5 - options for memory configuration figure 8 - memory configuration for: 2 banks, 1 layer, 2 mb total configuration 2 m per bank connections single layer (bootstrap pin tstout13 = open) two 256 k x 32 zbt sram/bank or one 256 k x 64 zbt sram/bank connect ads# to laye r 0 chipselect pin double layer (bootstrap pin tstout13 = pull down) four 128 k x 32 zbt sram/bank or two 128 k x 64 zbt sram/bank connect ads# to laye r 0 chipselect pin and 0e# to layer 1 chipselect pin frame data buffer only bank a bank a and bank b bank a and bank b 1m (sram) 2m (sram) 1m/bank (sram) 2m/bank (sram) 1 m/bank (zbt sram) 2m/bank (zbt sram) mvtx2601 x x mvtx2602 x x MVTX2603 x x MVTX2603 (gigabit ports in 2 giga mode) x (125 mhz) x (125 mhz) mvtx2604 x x mvtx2604 (gigabit ports in 2 giga mode) x (125 mhz) x (125 mhz) memory 128k 32 bits sram memory 128k 32 bits data la_d[63:32] data la_d[31:0] address la_a[19:3] bank a (1m one layer) b t t tstout7 o tstout13 o tstout4 o memory 128k 32 bits sram memory 128k 32 bits data lb_d[63:32] data lb_d[31:0] address lb_a[19:3] bank b (1m one layer)
MVTX2603 data sheet 22 zarlink semiconductor inc. figure 9 - memory configuration for: 2 banks, 2 layer, 4 mb total figure 10 - memory configuration for: 2 banks, 1 layer, 4 mb bank a (2m two layers) bank b (2m two layers) sram memory 128 k 32 bits sram memory 128 k 32 bits data lb_d[63:32] data lb_d[31:0] a ddress lb_a[19:3] sram memory 128 k 32 bits sram memory 128 k 32 bits sram memory 128 k 32 bits sram memory 128 k 32 bits data la_d[63:32] data la_d[31:0] a ddress la_a[19:3] sram memory 128 k 32 bits sram memory 128 k 32 bits bootstraps: tstout7 = pull down, tstout13 = pull down, tstout4 = open m c fi ti f 2 b k 2 l 4mb t t l a ddress la _ a[20:3] sram memory 256 k 32 bits memory 256 k 32 bits data la_d[63:32] data la_d[31:0] a ddress lb _ a[20:3] sram memory 256 k 32 bits memory 256 k 32 bits data lb_d[63:32] data lb_d[31:0] bank a (2m one layer) bank b (2m one layer) bootstraps: tstout7 = pull down, tstout13 = open, tstout4 = open
MVTX2603 data sheet 23 zarlink semiconductor inc. figure 11 - memory configuration for: 2 banks, 2 layers, 4 mb total figure 12 - memory configuration for: 2 banks, 1 layer, 4 mb bank a (2m two layers) bank b (2m two layers) zbt memory 128 k 32 bits zbt memory 128 k 32 bits data lb_d[63:32] data lb_d[31:0] a ddress lb _ a[19:3] zbt memory 128 k 32 bits zbt memory 128 k 32 bits zbt memory 128 k 32 bits zbt memory 128 k 32 bits data la_d[63:32] data la_d[31:0] a ddress la _ a[19:3] zbt memory 128 k 32 bits zbt memory 128 k 32 bits a ddress la _ a[20:3] zbt memory 256 k 32 bits zbt memory 256 k 32 bits data la_d[63:32] data la_d[31:0] a ddress lb_a[20:3] zbt memory 256 k 32 bits zbt memory 256 k 32 bits data lb_d[63:32] data lb_d[31:0] bank a (2m one layer) bank b (2m one layer) bootstraps: tstout7 = pull down, tstout13 = open, tstout4 = pull down
MVTX2603 data sheet 24 zarlink semiconductor inc. 6.0 frame engine 6.1 data forwarding summary ? when a frame enters the device at the rxmac, the rxdm a will move the data from the mac rxfifo to the fdb. data is moved in 8-byte granules in conj unction with the scheme for the sram interface. ? a switch request is sent to the search engine . the search engine processes the switch request. ? a switch response is sent back to the frame engine an d indicates whether the frame is unicast or multicast and its destination port or ports. ? a transmission scheduling request is sent in the form of a signal notifying the txq manager. upon receiving a transmission scheduling request, the device will format an entry in the appropriate transmission scheduling queue (txsch q) or queues. there are 4 txsch q for each 10/100 port (and 8 per gigabit port), one for each priority. creation of a queue entry either involves linking a new job to the appropriate linked list if unicast or adding an entry to a physical queue if multicast. ? when the port is ready to accept the next frame, the txq manager will get the head-of-line (hol) entry of one of the txsch qs, according to the transmission scheduling algorithm (to ensure per-class quality of service). the unicast linked list and the multicast qu eue for the same port-class pair are treated as one logical queue. the older hol between the two queues goes first. for 10/100 ports multicast queue 0 is associated with unicast queue 0 and multicast queue 1 is associated with unicast queue 2. for gigabit ports multicast queue 0 is associated with unicast queue 0, multicast queue 1 with unicast queue 2, multicast queue 2 with unicast queue 4 and multicast queue 3 with unicast queue 6. ? the txdma will pull frame data from the memory and fo rward it granule-by-granule to the mac txfifo of the destination port. 6.2 frame engine details this section briefly describes the functions of ea ch of the modules of the MVTX2603 frame engine. 6.2.1 fcb manager the fcb manager allocates fcb handles to incoming frames, and releases fcb handles upon frame departure. the fcb manager is also responsible for enforcing buffer reservations and limits. the default values can be determined by referring to chapter 8. in addition, the fcb manager is responsible for buffer aging and for linking unicast forwarding jobs to their correct txsch q. the buffer aging can be enabled or disabled by the bootstrap pin and the aging time is defined in register fcbat. 6.2.2 rx interface the rx interface is mainly responsible for communicating with the rxmac. it keeps track of the start and end of frame and frame status (good or bad). upon receiving an en d of frame that is good, the rx interface makes a switch request. 6.2.3 rxdma the rxdma arbitrates among switch requests from each rx interface. it also buffers the first 64 bytes of each frame for use by the search engine when the switch request has been made. 6.2.4 txq manager first, the txq manager checks the per-c lass queue status and glob al reserved resource si tuation, and using this information, makes the frame dropping decision after receiving a switch response. if the decision is not to drop, the txq manager requests that the fcb manager link the unicast frame?s fcb to the correct per-port-per-class txq. if multicast, the txq manager writes to the multicast queue for that port and class. the txq manager can also trigger
MVTX2603 data sheet 25 zarlink semiconductor inc. source port flow control for the inco ming frame?s source if that port is flow control enabled. second, the txq manager handles transmission scheduling; it schedules transmission among the queues representing different classes for a port. once a frame has been scheduled, the txq manager reads the fcb information and writes to the correct port control module. 6.3 port control the port control module calculates the sram read address fo r the frame currently being tr ansmitted. it also writes start of frame information and an end of frame flag to the mac txfifo. when transmission is done, the port control module requests that the buffer be released. 6.4 txdma the txdma multiplexes data and address from port control, and arbitrates among buffer release requests from the port control modules. 7.0 quality of se rvice and flow control 7.1 model quality of service is an all-encompassing term for which di fferent people have different interpretations. in general, the approach to quality of service described here assumes that we do not know the offered traffic pattern. we also assume that the incoming traffic is not policed or shaped. furthermore, we assume that the network manager knows his applications, such as voice, file transfer, or web browsing, and their relative importance. the manager can then subdivide the applications into classes and set up a service contract with each. the contract may consist of bandwidth or latency assurances per class. sometimes it may even reflect an estimate of the traffic mix offered to the switch. as an added bonus, although we do not assume anything about the arrival pattern, if the incoming traffic is policed or shaped, we may be able to provide addi tional assurances about our switch?s performance. table 6 on page 25 shows examples of qos applications with three transmission priorities, but best effort (p0) traffic may form a fourth class with no bandwidth or latency assurances. gigabit ports actually have eight total transmission priorities. goals total assured bandwidth (user defined) low drop probability (low-drop) high drop probability (high-drop) highest transmission priority, p3 50 mbps apps: phone calls, circuit emulation. latency: < 1 ms. drop: no drop if p3 not oversubscribed. apps: training video. latency: < 1 ms. drop: no drop if p3 not oversubscribed; first p3 to drop otherwise. middle transmission priority, p2 37.5 mbps apps: inte ractive apps, web business. latency: < 4-5 ms. drop: no drop if p2 not oversubscribed. apps: non-critical interactive apps. latency: < 4-5 ms. drop: no drop if p2 not oversubscribed; first p2 to drop otherwise. table 6 - two-dimensional world traffic
MVTX2603 data sheet 26 zarlink semiconductor inc. a class is capable of offering traffic that exceeds the contracted bandwidth. a well-behaved class offers traffic at a rate no greater than the agreed-upon rate. by contrast, a misbehaving class offers traffic that exceeds the agreed- upon rate. a misbehaving class is formed from an aggreg ation of misbehaving microflows. to achieve high link utilization, a misbehaving class is allowed to use any idle bandwidth. however, such leniency must not degrade the quality of service (qos) received by well-behaved classes. as table 6 illustrates, the six traffic types may each have their own distinct properties and applications. as shown, classes may receive bandwidth assurances or latency bounds. in the table, p3, the highest transmission class, requires that all frames be transmitted within 1 ms, and receives 50% of the 100 mbps of bandwidth at that port. best-effort (p0) traffic forms a fourth class that only receives bandwidth when none of the other classes have any traffic to offer. it is also possible to add a fourth class that has st rict priority over the other three; if this class has even one frame to transmit, then it goes first. in the MVTX2603, each 10/ 100 mbps port will support four total classes, and each 1000 mbps port will support eight cl asses. we will discuss the various modes of scheduling these classes in the next section. in addition, each transmission class has two subclasses, high-drop and low-drop. well-behaved users should rarely lose packets. but poorly behaved users ? users who send fr ames at too high a rate ? will encounter frame loss, and the first to be discarded will be high-drop. of course, if th is is insufficient to resolve the congestion, eventually some low-drop frames are dropped, and then all frames in the worst case. table 6 shows that different types of applications may be pl aced in different boxes in the traffic table. for example, casual web browsing fits into the category of high-loss, high-latency-tolerant traffic, whereas voip fits into the category of low-loss, low-latency traffic. 7.2 four qos configurations there are four basic pieces to qos scheduling in the mvtx 2603: strict priority (sp), delay bound, weighted fair queuing (wfq), and best effort (be). using these four pieces , there are four different mo des of operation, as shown in table 4, ?supported memory configur ations (zbt mode),? and table 6, ?t wo-dimensional world traffic,? . for 10/100 mbps ports, these modes are selected by the following registers: low transmission priority, p1 12.5 mbps apps: emails, file backups. latency: < 16 ms desired, but not critical. drop: no drop if p1 not oversubscribed. apps: casual web browsing. latency: < 16 ms desired, but not critical. drop: no drop if p1 not oversubscribed; first to drop otherwise. total 100 mbps qosc24 [7:6] credit_c00 qosc28 [7:6] credit_c10 qosc32 [7:6] credit_c20 qosc36 [7:6] credit_c30 table 6 - two-dimensional world traffic
MVTX2603 data sheet 27 zarlink semiconductor inc. these modes are selected by qosc40 [7:6] and qosc48 [7:6] for the first and second gigabit ports, respectively. the default configuration for a 10/100 mbps port is three delay-bounded queues and one best-effort queue. the delay bounds per class are 0.8 ms for p3, 2 ms for p2, and 12.8 ms for p1. for a 1 gbps port, we have a default of six delay-bounded queues and two best-effort queues. the delay bounds for a 1 gbps port are 0.16 ms for p7 and p6, 0.32 ms for p5, 0.64 ms for p4, 1.28 ms for p3, and 2.56 ms for p2. best effort traffic is only served when there is no delay-bounded traffic to be served. for a 1 gbps port, where there are two best-effort queues, p1 has strict priority over p0. we have a second configuration for a 10/100 mbps port in which there is one strict priority queue, two delay bounded queues, and one best effort queue. the delay bounds per class are 3.2 ms for p2 and 12.8 ms for p1. if the user is to choose this conf iguration, it is important t hat p3 (sp) traffic be either policed or implicitly bounded (e.g., if the incoming p3 traffic is very light and predic tably patterned). strict priori ty traffic, if not admission- controlled at a prior stage to the MVTX2603, can have an adverse effect on all other classes? performance. for a 1 gbps port, p7 and p6 are both sp classes and p7 has stri ct priority over p6. in this case, the delay bounds per class are 0.32 ms for p5, 0.64 ms for p4, 1.28 ms for p3, and 2.56 ms for p2. the third configuration for a 10/100 mbps port contains one strict priority queue and three queues receiving a bandwidth partition via wfq. as in the second configuration, strict priority traffic needs to be carefull y controlled. in the fourth configuration, all queues are served using a wfq service discipline. 7.3 delay bound in the absence of a sophisticated qos server and signaling protocol, the MVTX2603 may not know the mix of incoming traffic ahead of time. to cope with this uncertainty, our delay assurance algorithm dynamically adjusts its scheduling and dropping criteria, guided by the queue occupancies and the due dates of their head-of-line (hol) frames. as a result, we assure latency bounds for all admitt ed frames with high confidence, even in the presence of system-wide congestion. our algorithm identifies misbeh aving classes and intelligen tly discards frames at no detriment to well-behaved classes. our algorithm also di fferentiates between high-drop and low-drop traffic with a weighted random early drop (wred) approach. random early dropping prevents congestion by randomly dropping a percentage of high-drop frames even before the chip?s buffers are completely full, while still largely sparing low- drop frames. this allows high-drop frames to be discarded early, as a sacrifice for future low-drop frames. finally, the delay bound algorithm also achieves bandwidth partitioning among classes. p3 p2 p1 p0 op1 (default) delay bound be op2 sp delay bound be op3 sp wfq op4 wfq table 7 - four qos configurations for a 10/100 mbps port p7 p6 p5 p4 p3 p2 p1 p0 op1 (default) delay bound be op2 sp delay bound be op3 sp wfq op4 wfq table 8 - four qos configurations for a gigabit port
MVTX2603 data sheet 28 zarlink semiconductor inc. 7.4 strict priority and best effort when strict priority is part of the scheduling algorithm, if a queue has even one frame to transmit, it goes first. two of our four qos configurations include st rict priority queues. the goal is for stri ct priority classes to be used for ietf expedited forwarding (ef), where performance guarantees ar e required. as we have indicated, it is important that strict priority traffic be either policed or implicitly bounded, so as to keep from harming other traffic classes. when best effort is part of the scheduling algorithm, a queue only receives bandwidth when none of the other classes have any traffic to offer. two of our four qos configurations in clude best effort queues. the goal is for best effort classes to be used for non-essential traffic, becaus e we provide no assurances about best effort performance. however, in a typical network setting, much best effort traffic will indeed be transmitted and with an adequate degree of expediency. because we do not provide any delay assurances for best effort traffic, we do not enforce latency by dropping best effort traffic. furthermore, because we assume that strict priority traffic is carefully controlled before entering the MVTX2603, we do not enforce a fair bandwidth partition by dropping strict priority traffic. to summarize, dropping to enforce bandwidth or delay does not apply to strict priority or best effort queues. we only drop frames from best effort and strict priority queues when global buffer resources become scarce. 7.5 weighted fair queuing in some environments ? for example, in an environment in which delay assurances are not required, but precise bandwidth partitioning on small time scales is essential, wfq may be preferable to a delay-bounded scheduling discipline. the MVTX2603 provides the user with a wfq option with the understanding that delay assurances can not be provided if the incoming traffic pattern is uncontroll ed. the user sets four wfq ?weights? (eight for gigabit ports) such that all weights are whole numbers and sum to 64. this provides per-class bandwidth partitioning with error within 2%. in wfq mode, though we do not assure frame latency, the MVTX2603 still retains a set of dropping rules that helps to prevent congestion and trigger higher level protocol end-to-end flow control. as before, when strict priority is combined with wfq, we do not have special dropping rules for the strict priority queues, because the input traffic pattern is assumed to be carefully controlled at a prior stage. however, we do indeed drop frames from sp queues for global buffer management purposes. in addition, queue p0 for a 10/100 port (and queues p0 and p1 for a gigabit port) are treated as best effort from a droppi ng perspective, though they still are assured a percentage of bandwidth from a wfq scheduling perspective. what this means is that these particular queues are only affected by dropping when the global buffer count becomes low. 7.6 shaper although traffic shaping is not a primary function of t he MVTX2603, the chip does implement a shaper for expedited forwarding (ef). our goal in shaping is to control th e peak and average rate of traffic exiting the MVTX2603. shaping is limited to the two gigabit ports only, and only to class p6 (the second highest priority). this means that class p6 will be the class used for ef traffic. if shaping is enabled for p6, then p6 traffic must be scheduled using strict priority. with reference to table 8 only the middle two qos configurations may be used. peak rate is set using a programmable whole number, no grea ter than 64. for example, if the setting is 32, then the peak rate for shaped traffic is 32/64 * 1000 mbps = 500 mbps. average rate is also a programmable whole number, no greater than 64, and no greater than the peak rate. for example, if the setting is 16, then the average rate for shaped traffic is 16/64 * 1000 mbps = 250 mbps. as a cons equence of the above settings in our example, shaped traffic will exit the MVTX2603 at a rate always less than 500 mbps and averaging no greater than 250 mbps. see programming qos registers applic ation note for more information. also, when shaping is enabled, it is possible for a p6 queue to explode in length if fed by a greedy source. the reason is that a shaper is by definition not work-conserving; that is, it may hold back from sending a packet even if the line is idle. though we do have global resource management, we do nothing to prevent this situation locally. we assume sp traffic is policed at a prior stage to the MVTX2603.
MVTX2603 data sheet 29 zarlink semiconductor inc. 7.7 wred drop threshold management support to avoid congestion, the weighted random early detection (wred) logic drops packets according to specified parameters. the following table summarizes the behavior of the wred logic. table 9 - wred drop thresholds px is the total byte count, in the priority queue x. the wred logic has three drop levels, depending on the value of n, which is based on the number of bytes in the priori ty queues. if delay bound scheduling is used, n equals p3*16+p2*4+p1. if using wfq scheduling, n equals p3+p2+p1. each drop level from one to three has defined high-drop and low-drop percentages, which indicate the mi nimum and maximum percentages of the data that can be discarded. the x, y z percent can be programmed by the register rdrc0, rdrc1. in level 3, all packets are dropped if the bytes in each priority queue exceed the thre shold. parameters a, b, c are the byte count thresholds for each priority queue. they can be programmed by the qos control register (refer to the register group 5). 7.8 buffer management because the number of fdb slots is a scarce resource and because we want to ensure that one misbehaving source port or class cannot harm the performance of a well-behaved source port or class, we introduce the concept of buffer management into the MVTX2603. our buffer mana gement scheme is designed to divide the total buffer space into numerous reserved regions and one shared pool as shown in figure 13 on page 30. as shown in the figure, the fdb pool is divided into se veral parts. a reserved region for temporary frames stores frames prior to receiving a switch response. such a temporary region is necessary, because when the frame first enters the MVTX2603, its destination port and class are as yet unknown and so the decision to drop or not needs to be temporarily postponed. this ensures that every frame can be received first before subjecting them to the frame drop discipline after classifying. six reserved sections, one for each of the first six priority classes, ensure a programmable number of fdb slots per class. the lowest two classe s do not receive any buffer reservation. fu rthermore, even for 10/100 mbps ports, a frame is stored in the region of the fdb corresponding to it s class. as we have indicate d, the eight classes use only four transmission scheduling queues for 10/100 mbps ports, but as far as buffer usage is concerned, there are still eight distinguishable classes. another segment of the fdb reserves space for each of the 26 ports ethernet port. two parameters can be set, one for the source port reservation for 10 /100 mbps ports, and one for the source port reservation for 1 gbps ports. these 26 reserved regions make sure that no well-beha ved source port can be blocked by another misbehaving source port. in addition, there is a shared pool, whic h can store any type of frame. the fr ame engine allocates the frames first in the six priority sections. when the priority section is full or the packet has priority 1 or 0, the frame is allocated in the shared poll. once the shared poll is full the frames are allocated in the section reserved for the source port.
MVTX2603 data sheet 30 zarlink semiconductor inc. the following registers define the size of each section of the frame data buffer: figure 13 - buffer partition scheme used to implement MVTX2603 buffer management 7.8.1 dropping when buffers are scarce summarizing the two examples of local dropping discussed earlier in this chapter: ? if a queue is a delay-bounded queue, we have a multi-level wred drop scheme, designed to control delay and partition bandwidth in case of congestion. ? if a queue is a wfq-scheduled queue, we have a multi-level wred drop scheme, designed to prevent congestion. in addition to these reasons for dropping, we also drop frames when global buffer space becomes scarce. the function of buffer management is to make sure that such dropping causes as little blocking as possible. pr100- port reservation for 10/100 ports prg- port reservation for giga ports sfcb- share fcb size c2rs- class 2 reserve size c3rs- class 3 reserve size c4rs- class 4 reserve size c5rs- class 5 reserve size c6rs- class 6 reserve size c7rs- class 7 reserve size shared pool s per-source reservations (2 g) per-source reservations (24 10/100 m, cpu) temporary reservation per-class reservation
MVTX2603 data sheet 31 zarlink semiconductor inc. 7.9 MVTX2603 flow control basics because frame loss is unacceptable for some applicatio ns, the MVTX2603 provides a flow control option. when flow control is enabled, scarcity of buffer space in the sw itch may trigger a flow contro l signal; this signal tells a source port that is sending a packet to this switch to temporarily hold off. while flow control offers the clear benefit of no packet lo ss, it also introduces a problem for quality of service. when a source port receives an ethernet flow control signal, a ll microflows originating at that port, well-behaved or not, are halted. a single packet destined for a congested output can block other packets destined for uncongested outputs. the resulting head-of-line blocking phenomenon means that quality of service cannot be assured with high confidence when flow control is enabled. in the MVTX2603, each source port can independently have flow control enabled or disabled. for flow control enabled ports, by default all frames are treated as lowest priority during tran smission scheduling. this is done so that those frames are not exposed to the wred dropping scheme. frames from flow control enabled ports feed to only one queue at the destination, the queue of lowest priori ty. what this means is that if flow control is enabled for a given source port, then we can guarantee that no packets originating from that port will be lost, but at the possible expense of minimum bandwidth or maximum delay assura nces. in addition, these ?downgraded? frames may only use the shared pool or the per-source reserved pool in th e fdb; frames from flow control enabled sources may not use reserved fdb slots for th e highest six classes (p2-p7). the MVTX2603 does provide a system-w ide option of permitting normal qos scheduling (a nd buffer use) for frames originating from flow control enabled ports. when this programmable option is active, it is possible that some packets may be dropped, even though flow control is on. the reason is that intelligent packet dropping is a major component of the MVTX2603?s approach to ensuring bounded delay and minimum bandwidth for high priority flows. 7.9.1 unicast flow control for unicast frames, flow control is triggered by source port resource availability. recall that the MVTX2603?s buffer management scheme allocates a reserved number of fdb sl ots for each source port. if a programmed number of a source port?s reserved fdb slots have been used, then flow control xoff is triggered. xon is triggered when a port is currently being flow contro lled, and all of that port?s reserved fdb slots have been released. note that the MVTX2603?s per-source-port fdb reservations assure that a sour ce port that sends a single frame to a congested destination will not be flow controlled. 7.9.2 multicast flow control in unmanaged mode, flow cont rol for multicast frames is triggered by a global buffer co unter. when the system exceeds a programmable threshol d of multicast packets, xoff is triggered. xon is triggered wh en the system returns below this threshold. in managed mode, per-vlan flow control is used for multicast frames. in this case, flow control is triggered by congestion at the destination. how so? the MVTX2603 ch ecks each destination to which a multicast packet is headed. for each destination port, the occupancy of the lowest-priority transmission multicast queue (measured in number of frames) is compared against a programmable co ngestion threshold. if congestion is detected at even one of the packet?s destinations then xoff is triggered. in addition, each source port has a 26-bit port map recording which port or ports of the multicast frame?s fanout were congested at the time xoff was triggered. all ports are continuously monitored for congestion, and a port is identified as uncongested when its queue occupancy falls below a fixed threshold. when all those ports that were originally marked as congested in the port map have be come uncongested, then xon is triggered and the 26-bit vector is reset to zero.
MVTX2603 data sheet 32 zarlink semiconductor inc. the MVTX2603 also provides the option of disabling vlan multicast flow control. note : if per-port flow control is on, qos performance will be affected. to determine the most efficient way to program, please refer to the qos application note. 7.10 mapping to ietf diffserv classes the mapping between priority classes discussed in this chapter and elsewhere is shown below. as the table illustrates, p7 is used solely for netw ork management (nm) frames. p6 is used for expedited forwarding service (ef). classe s p2 through p5 correspond to an assured forwarding (af) group of size 4. finally, p0 and p1 are two best effort (be) classes. for 10/100 mbps ports, the classes of table 12 are merged in pairs?one class corresponding to nm+ef, two af classes, and a single be class. features of the MVTX2603 that correspond to the requirem ents of their associated ietf classes are summarized in the table below. vtx p7 p6 p5 p4 p3 p2 p1 p0 ietf nm ef af0 af1 af2 af3 be0 be1 table 10 - mapping between MVTX2603 and ietf diffserv classes for gigabit ports vtx p3p2p1p0 ietf nm+ef af0 af1 be0 table 11 - mapping between MVTX2603 and ietf diffserv classes for 10/100 ports network manage ment (nm) and expedited forwarding (ef) ? global buffer reservation for nm and ef ? shaper for ef traffic on 1 gbps ports ? option of strict priority scheduling ? no dropping if admission controlled assured forwarding (af) ? four af classes for 1 gbps ports ? programmable bandwidth partition, with option of wfq service ? option of delay-bounded service keeps delay under fixed levels even if not admission-controlled ? random early discard, with programmable levels ? global buffer reservation for each af class best effort (be) ? two be classes for 1 gbps ports ? service only when other queues are idle means that qos not adversely affected ? random early discard, with programmable levels ? traffic from flow control enabled ports automatically classified as be table 12 - MVTX2603 features enabling ietf diffserv standards
MVTX2603 data sheet 33 zarlink semiconductor inc. 8.0 port trunking 8.1 features and restrictions a port group (i.e., trunk) can include up to 4 physical po rts but all of the ports in a group must be in the same MVTX2603. the two gigabit ports may also be trunked together. there are three trunk groups total including the option to trunk gigabit ports. load distribution among the ports in a trunk for unicast is performed using hashing based on source mac address and destination mac address. three other options incl ude source mac address only, destination mac address only and source port (in bidirectional ring mode onl y). load distribution for multicast is performed similarly. if a vlan includes any of the ports in a trunk group, all the ports in that trunk group should be in the same vlan member map. the MVTX2603 also provides a safe fail-over mode for port trunking automatically. if one of the ports in the trunking group goes down, the MVTX2603 will automatically redistribute the traffic over to the remaining ports in the trunk. 8.2 unicast packet forwarding the search engine finds the destination mct entry, and if the status field says that the destination port found belongs to a trunk, then the group number is retrieved inst ead of the port number. in addition, if the source address belongs to a trunk, then the source port? s trunk membership re gister is checked. a hash key, based on some combination of the source and destination mac addresses for the current packet selects the appropriate forwarding port. 8.3 multicast packet forwarding for multicast packet forwarding, the de vice must determine the proper set of ports from which to transmit the packet based on the vlan index and hash key. two functions are required in order to distribute multic ast packets to the appropriate destination ports in a port trunking environment. determining one forwarding port per group. for multicast packets, all but one port per group, the forwarding port, must be excluded. preventing the multicast packet from looping back to the source trunk. the search engine needs to prevent a multicast packet from sending to a port that is in the same trunk group with the source port. this is because, when we select the pr imary forwarding port for each group, we do not take the source port into account. to prevent this, we simply apply one additional filter, so as to block that forwarding port for this multicast packet.
MVTX2603 data sheet 34 zarlink semiconductor inc. 8.4 trunking 3 trunk groups are supported. groups 0 and 1 can trunk up to 4 10/100 ports. group 2 can trunk 2 gigabit ports. the supported combinations are shown in the following table. select via trunk0_mode register select via trunk1_mode register the trunks are individually enabled/disabled by controlling pin trunk 0, 1, 2. 9.0 port mirroring 9.1 port mirroring features the received or transmitted data of any 10/100 port in the MVTX2603 chip can be ?mirrored? to any other port. we support two such mirrored source-destination pairs. a mirror port cannot also serve as a data port. please refer to the port mirroring applicati on note for further details. 9.2 setting registers for port mirroring ? mirror1_src: sets the source port for the first port mirroring pair. bi ts [4:0] select the source port to be mirrored. an illegal port number is used to disable mirr oring (which is the default se tting). bit [5] is used to select between ingress (rx) or egress (tx) data. ? mirror1_dest: sets the destination port for the first port mirroring pair. bits [4:0] select the destination port to be mirrored. the default is port 23. ? mirror2_src: sets the source port for the second port mirroring pair . bits [4:0] select the source port to be mirrored. an illegal port number is used to disable mirroring (which is the default setting). bit [5] is used to select between ingress (rx) or egress (tx) data. ? mirror2_dest: sets the destination port for the second port mirrorin g pair. bits [4:0] select the destination port to be mirrored. the default is port 0. group 0 port 0 port 1 port 2 port 3 xx xxx x xxx group 1 port 4 port 5 port 6 port 7 xx x xxx group 2 port 25(giga 0) port 26 (giga 1) xx
MVTX2603 data sheet 35 zarlink semiconductor inc. 10.0 tbi interface the tbi interface can be used for 1000mbps fiber operation. in this mode, the MVTX2603 is connected to the serdes as shown in figure 14. there are two tbi interfaces in the MVTX2603 devices. to enable to tbi function, the corresponding txen and txer pins need to be boot strapped. see ball ? signal description for details. figure 14 - tbi connection MVTX2603 serdes m25/26_txd[9:0] m25/26_txclk m25/26_rxclk m25/26_col m25/26_rxd[9:0] rbc0 rbc1 t[9:0] r[9:0] refclk
MVTX2603 data sheet 36 zarlink semiconductor inc. 11.0 gpsi (7ws) interface 11.1 gpsi connection the 10/100 rmii ethernet port can fu nction in gpsi (7ws) mode when the corresponding txen pin is strapped low with a 1 k pull down resistor. in this mode, the txd[0] , txd[1], rxd[0] and rxd[1] serve as tx data, tx clock, rx data and rx clock respectively. the link status and collision from the phy are multiplexed and shifted into the switch device through external glue logic. the duplex of the port can be controlled by programming the ecr register. the gpsi interface can be operated in port based vlan mode only figure 15 - gpsi (7ws) mode connection diagram crs_dv rxd[0] rxd[1] txd[1] txd[0] txen port 0 ethernet phy 260x scan_col scan_clk scan_link ethernet port 23 ethernet phy ethernet link serializer (cpld) collision serializer (cpld) crs rxd rx_clk tx_clk txd txen link0 col0 link1 col1 link2 col2 link23 col23
MVTX2603 data sheet 37 zarlink semiconductor inc. 11.2 scan link and scan col interface an external cpld logic is required to take the link signal s and collision signals from the gpsi phys and shift them into the switch device. the switch device will drive out a signature to indicate the start of the sequence. after that, the cpld should shift in the link and collision status of the phys as shown in the figure. the extra link status indicates the polarity of the link signal. one indicates the polarity of the link signal is active high. figure 16 - scan link and scan collison status diagram 12.0 led interface 12.1 led interface introduction a serial output channel provides port status information from the MVTX2603 chips. it requires three additional pins: ? led_clk at 12.5 mhz ? led_syn a sync pulse that defines the boundary between status frames ? led_data a continuous serial stream of data for all status leds that repeats once every frame time a non-serial interface is also allowed, but in this ca se, only the gigabit ports will have status leds. a low cost external device (44 pin pal) is used to decode the serial data and to drive an led array for display. this device can be customiz ed for different needs. 12.2 port status in the MVTX2603, each port has 8 status indicators, each represented by a single bit. the 8 led status indicators are ? bit 0: flow control ? bit 1:transmit data ? bit 2: receive data ? bit 3: activity (where ac tivity includes either transmission or reception of data) ? bit 4: link up ? bit 5: speed (1= 100 mb/s; 0= 10 mb/s) ? bit 6: full-duplex ? bit 7: collision eight clocks are required to cycle through the eight status bits for each port. scan_clk scan_link/ scan_col drived by vtx260x drived by cpld 25 cycles for link/ 24 cycles for col total 32 cycles period driven by mvtx260x driven by cpld total 32 cycles period
MVTX2603 data sheet 38 zarlink semiconductor inc. when the led_syn pulse is asserted, the led inte rface will present 256 led cl ock cycles with the clock cycles providing information for the following ports. port 0 (10/100): cycles #0 to cycle #7 port 1 (10/100): c ycles#8 to cycle #15 port 2 (10/100): c ycle #16 to cycle #23 ... port 22 (10/100): cycl e #176 to cycle #183 port 23 (10/100): cycle #184 to cycle #191 port 24 (gigabit 0): cycle #192 to cycle #199 port 25 (gigabit 1): cycle #200 to cycle #207 byte 26 (additional status ): cycle #208 to cycle #215 byte 27 (additional status ): cycle #216 to cycle #223 cycles #224 to 256 present data with a value of zero. the first two bits of byte 26 provides the speed information for the gigabit ports while the remainder of byte 26 and byte 27 provides bit status ? 26[0]: g0 port (1= port 24 is operating at gigabit speed; 0= speed is either 10 or 100 mb/s depending on speed bit of port 24) ? 26[1]: g1 port (1= port 25 is operating at gigabit speed; 0= speed is either 10 or 100 mb/s depending on speed bit of port 25) ? 26[2]: initialization done ? 26[3]: initialization start ? 26[4]: checksum ok ? 26[5]: link_init_complete ? 26[6]: bist_fail ? 26[7]: ram_error ? 27[0]: bist_in_process ? 27[1]: bist_done 12.3 led interface timing diagram the signal from the MVTX2603 to the led decoder is shown in figure 17. figure 17 - timing diagram of led interface
MVTX2603 data sheet 39 zarlink semiconductor inc. 13.0 register definition 13.1 MVTX2603 register description register description cpu addr (hex) r/w i 2 c addr (hex) default notes 0. ethernet port control re gisters substitute [n] with port number (0..17h, 19h, 1ah) ecr1p?n? port control register 1 for port n 0000 + 2 x n r/w 000-018 020 ecr2p?n? port control register 2 for port n 001 + 2 x n r/w 01b-033 000 1. vlan control registers substitute [n] with port number (0..17h, 19h, 1ah) avtcl vlan type code register low 100 r/w 036 000 avtch vlan type code register high 101 r/w 037 081 pvmap?n?_0 port ?n? configuration register 0 102 + 4n r/w 038-052 0ff pvmap?n?_1 port ?n? configuration register 1 103 + 4n r/w 053-06d 0ff pvmap?n?_2 port ?n? configuration register 2 104 + 4n r/w 06e-088 0ff pvmap?n?_3 port ?n? configuration register 3 105 + 4n r/w 089-0a3 007 pvmode vlan operating mode 170 r/w 0a4 000 2. trunk control registers trunk0_ mode trunk group 0 mode 203 r/w 0a5 003 trunk1_ mode trunk group 1 mode 20b r/w 0a6 003 trunk2_ mode trunk group 2 mode 210 r/w na 003 tx_age transmission queue aging time 325 r/w 0a7 008 3. search engine configurations agetime_low mac address aging time low 400 r/w 0a8 2m:05c/ 4m:02e agetime_ high mac address aging time high 401 r/w 0a9 000 se_opmode search engine operating mode 403 r/w na 000 4. buffer control and qos control fcbat fcb aging timer 500 r/w 0aa 0ff qosc qos control 501 r/w 0ab 000 fcr flooding control register 502 r/w 0ac 008 avpml vlan priority map low 503 r/w 0ad 000 avpmm vlan priority map middle 504 r/w 0ae 000 avpmh vlan priority map high 505 r/w 0af 000 tospml tos priority map low 506 r/w 0b0 000 tospmm tos priority map middle 507 r/w 0b1 000
MVTX2603 data sheet 40 zarlink semiconductor inc. tospmh tos priority map high 508 r/w 0b2 000 avdm vlan discard map 509 r/w 0b3 000 tosdml tos discard map 50a r/w 0b4 000 bmrc broadcast/multicast rate control 50b r/w 0b5 000 ucc unicast congestion control 50c r/w 0b6 2m:008/ 4m:010 mcc multicast congestion control 50d r/w 0b7 050 pr100 port reservation for 10/100 ports 50e r/w 0b8 2m:024/ 4m:036 sfcb share fcb size 510 r/w 0ba 2m:014/ 4m:064 c2rs class 2 reserve size 511 r/w 0bb 000 c3rs class 3 reserve size 512 r/w 0bc 000 c4rs class 4 reserve size 513 r/w 0bd 000 c5rs class 5 reserve size 514 r/w 0be 000 c6rs class 6 reserve size 515 r/w 0bf 000 c7rs class 7 reserve size 516 r/w 0c0 000 qosc?n? qos control (n=0 59) 517 512 r/w 0c1-0d2 000 rdrc0 wred drop rate control 0 553 r/w 0fb 08f rdrc1 wred drop rate control 1 554 r/w 0fc 088 user_ port?n?_low user define logical port ?n? low (n=0-7) 580 + 2n r/w 0d6-0dd 000 user_ port?n?_high user define logical port ?n? high 581 + 2n r/w 0de-0e5 000 user_ port1:0_ priority user define logic port 1 and 0 priority 590 r/w 0e6 000 user_ port3:2_ priority user define logic port 3 and 2 priority 591 r/w 0e7 000 user_ port5:4_ priority user define logic port 5 and 4 priority 592 r/w 0e8 000 user_ port7:6_pri ority user define logic port 7 and 6 priority 593 r/w 0e9 000 user_port_ enable user define logic port enable 594 r/w 0ea 000 wlpp10 well known logic port priority for 1 and 0 595 r/w 0eb 000 wlpp32 well known logic port priority for 3 and 2 596 r/w 0ec 000 register description cpu addr (hex) r/w i 2 c addr (hex) default notes
MVTX2603 data sheet 41 zarlink semiconductor inc. wlpp54 well known logic port priority for 5 and 4 597 r/w 0ed 000 wlpp76 well-known logic port priority for 7 & 6 598 r/w 0ee 000 wlpe well known logic port enable 599 r/w 0ef 000 rlowl user define range low bit7:0 59a r/w 0f4 000 rlowh user define range low bit 15:8 59b r/w 0f5 000 rhighl user define range high bit 7:0 59c r/w 0d3 000 rhighh user define range high bit 15:8 59d r/w 0d4 000 rpriority user define range priority 59e r/w 0d5 000 5. misc configuration registers mii_op0 mii register option 0 600 r/w 0f0 000 mii_op1 mii register option 1 601 r/w 0f1 000 fen feature registers 602 r/w 0f2 010 miic0 mii command register 0 603 r/w n/a 000 miic1 mii command register 1 604 r/w n/a 000 miic2 mii command register 2 605 r/w n/a 000 miic3 mii command register 3 606 r/w n/a 000 miid0 mii data register 0 607 ro n/a n/a miid1 mii data register 1 608 ro n/a n/a led led control register 609 r/w 0f3 000 sum eeprom checksum register 60b r/w 0ff 000 6. port mirroring controls mirror1_src port mirror 1 source port 700 r/w n/a 07f mirror1_ dest port mirror 1 destination port 701 r/w n/a 017 mirror2_src port mirror 2 source port 702 r/w n/a 0ff mirror2_ dest port mirror 2 destination port 703 r/w n/a 000 f. device configuration register gcr global control register f00 r/w n/a 000 dcr device status and signature register f01 ro n/a n/a dcr1 giga port status f02 ro n/a n/a dpst device port status register f03 r/w n/a 000 dtst data read back register f04 ro n/a n/a da da register fff ro n/a da register description cpu addr (hex) r/w i 2 c addr (hex) default notes
MVTX2603 data sheet 42 zarlink semiconductor inc. 13.2 group 0 address mac ports group 13.2.1 ecr1pn: port n control register ?i 2 c address h000-01a; cpu address: 0000+2xn ? accessed by serial interface and i 2 c (r/w) 76 5432 1 0 sp state a-fc port mode bit [0] ? 1 - flow control off ? 0 - flow control on ? when flow control on: ? in half duplex mode, the ma c transmitter applies back pr essure for flow control. ? in full duplex mode, the mac transmitt er sends flow control frames when necessary. the mac receiver interprets and processes incoming flow control frames. the flow control frame rece ived counter is incremented whenever a flow control is received. ? when flow control off: ? in half duplex mode, the mac transmitter does not assert flow control by sending flow control frames or jamming collision. ? in full duplex mode, the mac transmitter does not send flow c ontrol frames. the mac receiver does not interpret or proc ess the flow control frames. the flow control frame received c ounter is not incremented. bit [1] ? 1 - half duplex - only 10/100 mode ? 0 - full duplex bit [2] ? 1 - 10 mbps ? 0 - 100 mbps bit [4:3] ? 00 - automatic enable auto neg. this enables hardware state machine for auto-negotiation. ? 01 - limited disable auto neg. this disables hardware for speed auto- negotiation. poll mii for link status. ? 10 - link down. disable auto neg. state machine and force link down (disable the port) ? 11 - link up. user er c1 [2:0] for config. bit [5] ? asymmetric flow control enable ? 0 - disable asymmetric flow control ? 1 - enable asymmetric flow control ? asymmetric flow control enable. when this bit is set and flow control is on (bit [0] = 0, don't send out a flow cont rol frame. but mac receiver interprets and process flow control frames. default is 0 bit [7:6] ? ss - spanning tree state default is 11 ? 00 ? blocking: frame is dropped ? 01 - listening: frame is dropped ? 10 - learning: frame is dropped. source mac address is learned. ? 11 - forwarding: frame is fo rwarded. source mac address is learned.
MVTX2603 data sheet 43 zarlink semiconductor inc. 13.2.2 ecr2pn: port n control register ?i 2 c address: h01b-035; cpu address: h0001+2xn ? accessed by and serial interface and i 2 c (r/w) 13.2.3 ggcontrol ? extra giga port control ? cpu address: h036 ? accessed by serial interface (r/w) 765 4 3 2 1 0 qos sel reserve disl ftf futf bit [0]: ? filter untagged frame (default 0) ? 0: disable ? 1: all untagged frames from this port are discarded bit [1]: ? filter tag frame (default 0) ? 0: disable ? 1: all tagged frames from this port are discarded bit [2]: ? learning disable (default 0) ? 1 learning is disabled on this port ? 0 learning is enabled on this port bit [3]: ? must be set to ?1? bit [5:4:] ? qos mode selection (default 00) ? determines which of the 4 sets of qo s settings is used for 10/100 ports. ? note that there are 4 sets of per-queue byte thresholds, and 4 sets of wfq ratios programmed. these bits select among the 4 choices for each 10/100 port. refer to qos application note. ? 00: select class byte limit set 0 and classes wfq credit set 0 ? 01: select class byte limit set 1 and classes wfq credit set 1 ? 10: select class byte limit set 2 and classes wfq credit set 2 ? 11: select class byte limit set 3 and classes wfq credit set 3 bit [7:6] ? reserved 7654321 0 df miib rsta df miia rsta bit [0]: ? reset giga port a ? 0: normal operation (default) ? 1: reset gigabit port a bit [1]: ? giga port a use mii interface (10/100 m) ? 0: gigabit port operations at 1000 mode ? 1: gigabit port operations at 10/100 mode bit [2]: ? reserved - must be zero
MVTX2603 data sheet 44 zarlink semiconductor inc. 13.3 group 1 address vlan group 13.3.1 avtcl ? vlan type code register low ?i 2 c address h036; cpu address: h100 ? accessed by serial interface and i 2 c (r/w) 13.3.2 avtch ? vlan type code register high ?i 2 c address h037; cpu address: h101 ? accessed by serial interface and i 2 c (r/w) 13.3.3 pvmap00_0 ? port 00 configuration register 0 ?i 2 c address h038, cpu address: h102 ? accessed by serial interface and i 2 c (r/w) this register indicates the legal egress ports. a ?1? on bit 7 means that the packet can be sent to port 7. a ?0? on bit 7 means that any packet destined to port 7 will be discarded . this register works with registers 1, 2 and 3 to form a 27 bit mask to all egress ports. bit [3]: ? giga port a direct flow control (mac to mac connection ). the MVTX2603 supports direct flow control mechanism, the flow control frame is therefore not sent through the gigabit port data path. ? 0: direct flow control disabled (default) ? 1: direct flow control enabled bit [4]: ? reset giga port b ? 0: normal operation (default) ? 1: reset gigabit port b bit [5]: ? giga port b use mii interface (10/100 m) ? 0: gigabit port operates at 1000 mode ? 1: gigabit port operates at 10/100 mode bit [6]: ? reserved. must be zero. bit [7]: ? giga port b direct flow control (mac to mac connection ). the MVTX2603 supports direct flow control mechanism, the flow control frame is therefore not sent through the gigabit port data path. ? 0: direct flow control disabled (default) ? 1: direct flow control enabled bit [7:0]: ? vlantype_low: lower 8 bits of the vlan type code (default 00) bit [7:0]: ? vlantype_high: upper 8 bits of the vlan type code (default is 81) bit [7:0]: ? vlan mask for ports 7 to 0 (default ff)
MVTX2603 data sheet 45 zarlink semiconductor inc. 13.3.4 pvmap00_1 ? port 00 configuration register 1 ?i 2 c address h53, cpu address: h103 ? accessed by serial interface and i 2 c (r/w) 13.3.5 pvmap00_2 ? port 00 configuration register 2 ?i 2 c address h6e, cpu address: h104 ? accessed by serial interface and i 2 c (r/w) 13.3.6 pvmap00_3 ? port 00 configuration register 3 ?i 2 c address h89, cpu address: h105 ? accessed by serial interface and i 2 c (r/w) bit [7:0]: ? vlan mask for ports 15 to 8 (default is ff) bit [7:0]: ? vlan mask for po rts 23 to 16 (default ff) 765 3210 fp en drop default tx priority vlan mask bit [0]: reserved (default 1) bit [2:1]: vlan mask for ports 26 to 25 (default 3) bit [5:1]: default transmit prio rity. used when bit [7] = 1 (default 0) ? 000 transmit priority level 0 (lowest) ? 001 transmit priority level 1 ? 010 transmit priority level 2 ? 011 transmit priority level 3 ? 100 transmit priority level 4 ? 101 transmit priority level 5 ? 110 transmit priority level 6 ? 111 transmit priority level 7 (highest) bit [6]: default discard priority (default 0) ? 0 - discard priority level 0 (lowest) ? 1 - discard priority level 7(highest) bit [7]: enable fix priority (default 0) ? 0 disable fix priority. all frames are analysed. transmit priority and discard priority are based on vlan tag, tos field or logical port. ? 1 transmit priority and discard priority are based on values programmed in bit [6:3]
MVTX2603 data sheet 46 zarlink semiconductor inc. 13.4 port configuration register ? pvmap01_0,1,2,3 i 2 c address h39,54,6f,8a; cpu address:h106,107,108,109) ? pvmap02_0,1,2,3 i 2 c address h3a,55,70,8b; cpu address:h10a, 10b, 10c, 10d) ? pvmap03_0,1,2,3 i 2 c address h3b,56,71,8c; cpu address:h10e, 10f, 110, 111) ? pvmap04_0,1,2,3 i 2 c address h3c,57,72,8d; cpu address:h112, 113, 114, 115) ? pvmap05_0,1,2,3 i 2 c address h3d,58,73,8e; cpu address:h116, 117, 118, 119) ? pvmap06_0,1,2,3 i 2 c address h3e,59,74,8f; cpu address:h11a, 11b, 11c, 11d) ? pvmap07_0,1,2,3 i 2 c address h3f,5a,75,90; cpu address:h11e, 11f, 120, 121) ? pvmap08_0,1,2,3 i 2 c address h40,5b,76,91; cpu address:h122, 123, 124, 125) ? pvmap09_0,1,2,3 i 2 c address h41,5c,77,92; cpu address:h126, 127, 128, 129) ? pvmap10_0,1,2,3 i 2 c address h42,5d,78,93; cpu address:h12a, 12b, 12c, 12d) ? pvmap11_0,1,2,3 i 2 c address h43,5e,79,94; cpu address:h12e, 12f, 130, 131) ? pvmap12_0,1,2,3 i 2 c address h44,5f,7a,95; cpu address:h132, 133, 134, 135) ? pvmap13_0,1,2,3 i 2 c address h45,60,7b,96; cpu address:h136, 137, 138, 139) ? pvmap14_0,1,2,3 i 2 c address h46,61,7c,97; cpu address:h13a, h13b, 13c, 13d) ? pvmap15_0,1,2,3 i 2 c address h47,62,7d,98; cpu address:h13e, 13f, 140, 141) ? pvmap16_0,1,2,3 i 2 c address h48,63,7e,99; cpu address:h142, 143, 144, 145) ? pvmap17_0,1,2,3 i 2 c address h49,64,7f,9a; cpu address:h146, 147, 148, 149) ? pvmap18_0,1,2,3 i 2 c address h4a,65,80,9b; cpu address:h14a, 14b, 14c, 14d) ? pvmap19_0,1,2,3 i 2 c address h4b,66,81,9c; cpu address:h14e, 14f, 150, 151) ? pvmap20_0,1,2,3 i 2 c address h4c,67,82,9d; cpu address:h152, 153, 154, 155) ? pvmap21_0,1,2,3 i 2 c address h4d,68,83,9e; cpu address:h156, 157, 158, 159) ? pvmap22_0,1,2,3 i 2 c address h4e,69,84,9f; cpu address:h15a, 15b, 15c, 15d) ? pvmap23_0,1,2,3 i 2 c address h4f,6a,85,a0; cpu address:h15e, 15f, 160, 161) ? pvmap25_0,1,2,3 i 2 c address h51,6c,87,a2; cpu address:h166, 167, 168, 169) (gigabit port 1) ? pvmap26_0,1,2,3 i 2 c address h52,6d,88,a3; cpu address:h16a, 16b, 16c, 16d) (gigabit port 2) 13.4.1 pvmode ?i 2 c address: h0a4, cpu address: h170 ? accessed by serial interface, and i 2 c (r/w) 7543210 sm0 rpcs df sl bit [0]: ? reserved ? must be ?0? bit [1]: ? slow learning same function as se_op mode bit 7. either bit can enable the function; both need to be turned off to disable the feature. bit [2]: ? disable dropping of frames with destination mac addresses 0180c2000001 to 0180c200000f (default = 0) ? 0: drop all frames in this range ? 1: disable dropping of frames in this range bit [3]: ? 1: disable reset pcs ? 0: enable reset pcs. pcs fifo will be reset when receiving a pcs symbol error
MVTX2603 data sheet 47 zarlink semiconductor inc. 13.4.2 trunk0_mode? trunk group 0 mode ?i 2 c address: h0a5; cpu address: h203 ? accessed by serial interface and i 2 c (r/w) 13.4.3 trunk1_mode ? trunk group 1 mode ?i 2 c address: h0a6; cpu address: h20b ? accessed by serial interface and i 2 c (r/w) bit [4]: ? support mac address 0 ? 0: mac address 0 is not learned. ? 1: mac address 0 is learned. bit [7:5]: ? reserved 7 43 210 hash select port select bit [1:0]: ? port selection in unmanaged mode. input pin trunk0 enable/disable trunk group 0 ? 00 reserved ? 01 port 0 and 1 are used for trunk 0 ? 10 port 0,1 and 2 are used for trunk 0 ? 11 port 0,1,2 and 3 are used for trunk 0 bit [3:2] ? hash select. the hash selected is valid for trunk 0, 1 and 2. (default 00) ? 00 use source and destination mac address for hashing ? 01 use source mac address for hashing ? 10 use destination mac address for hashing ? 11 use source destination mac address and ingress physical port number for hashing note : trunk group 2 (two gigabit ports) is enabled/disabled using input pin trunk2. 7210 port select bit [1:0]: ? port selection in unmanaged mode. input pin trunk1 enable/disable trunk group 1 ? 00 reserved ? 01 port 4 and 5 are used for trunk1 ? 10 reserved ? 11 port 4, 5, 6 and 7 are used for trunk1
MVTX2603 data sheet 48 zarlink semiconductor inc. 13.5 group 4 address search engine group 13.5.1 tx_age ? tx queue aging timer ?i 2 c address: h07;cpu address: h325 ? accessed by serial interface (rw) ? bit [5:0]: unit of 100 ms (default 8) ? disable transmission queue aging if value is zero. aging timer for all ports and queues. ? for no packet loss flow control, this register mu st be set to 0. 13.5.2 agetime_low ? mac address aging time low ?i 2 c address: h0a8; cpu address: h400 ? accessed by serial interface and i 2 c (r/w) ? bit [7:0] low byte of th e mac address aging timer. ? mac address aging is enable/disable by boot strap tstout9 13.5.3 agetime_high ?mac address aging time high ?i 2 c address: h0a9; cpu address: h401 ? accessed by serial interface and i 2 c (r/w) ? bit [7:0]: high byte of th e mac address aging timer. ? the default setting provide 300 seconds aging time. aging time is based on the following equation: ? {agetime_high,agetime_low} x (# of ma c address entries in the memory x 100 sec). number of mac entries = 32 k when 1 mb is used per bank. numb er of mac entries = 64 k when 2 mb is used per bank. 13.5.4 se_opmode ? search engine operation mode ? cpu address: h403 ? accessed by serial interface (r/w) ? {se_opmode} x(# of entries 100 u sec) 765 0 tx queue agent 765 0 sl dms bit [5:0]: ? reserved bit [6]: ? disable mct speedup aging ? 1 ? disable speedup aging when mct resource is low. ? 0 ? enable speedup aging when mct resource is low. bit [7]: ? slow learning ? 1? enable slow learning. learning is temporary disabled when search demand is high ? 0 ? learning is performed independent of search demand
MVTX2603 data sheet 49 zarlink semiconductor inc. 13.6 group 5 address buffer control/qos group 13.6.1 fcbat ? fcb aging timer ?i 2 c address: h0aa; cpu address: h500 13.6.2 qosc ? qos control ?i 2 c address: h0ab; cpu address: h501 ? accessed by serial interface and i 2 c (r/w) 13.6.3 fcr ? flooding control register ?i 2 c address: h0ac; cpu address: h502 ? accessed by serial interface and i 2 c (r/w) 70 fcbat bit [7:0]: ? fcb aging ti me. unit of 1ms. ( default ff ) ? this function is for buffer aging control. it is used to configure the aging time, and can be enabled/ disabled through bootstrap pin. it is not recommended to use this fu nction for normal operation. 76 5 43 10 tos-d tos-p vf1c l bit [0]: ? qos frame lost is ok. priority will be available for flow control enabled source only when th is bit is set (default 0) bit [4]: ? per vlan multicast flow control (default 0) ? 0 - disable ? 1 - enable bit [5]: ? reserved bit [6]: ? select tos bits for priority (default 0) ? 0 - use tos [4:2] bits to map the transmit priority ? 1 - use tos [7:5] bits to map the transmit priority bit [7]: ? select tos bits for drop priority (default 0) ?0 - use tos[4:2] bits to map the drop priority ? 1 - use tos[7:5] bits to map the drop priority 76 43 0 tos timebase u2mr
MVTX2603 data sheet 50 zarlink semiconductor inc. 13.6.4 avpml ? vlan priority map ?i 2 c address: h0ad; cpu address: h503 ? accessed by serial interface and i 2 c (r/w) registers avpml, avpmm, and avpmh allow the eight vlan priorities to map into eight internal level transmit priorities. under the internal transmit priority, seven is hi ghest priority where as zero is the lowest. this feature allows the user the flexibility of redefining the vlan priori ty field. for example, programming a value of 7 into bit 2:0 of the avpml register would map vlan priority 0 into internal transmit priority 7. the new priority is used inside the 2603. when the packet goes out it carries the original priority. bit [3:0]: ? u2mr: unicast to multicast rate. units in terms of ti me base defined in bits [6:4]. this is used to limit the amount of flooding traffic. the value in u2mr specifies how many packets are allowe d to flood within the time specified by bit [6:4]. to disabl e this function, pr ogram u2mr to 0. ( default = 8 ) bit [6:4]: ? timebase: 000 = 100 us 001 = 200 us 010 = 400 us 011 = 800 us 100 = 1.6 ms 101 = 3.2 ms 110 = 6.4 ms 111 = 100 us (same as 000) ? (default = 000) bit [7]: ? select vlan tag or tos (ip packets) to be preferentially picked to map transmit priority and drop priority ( default = 0 ). ? 0 ? select vlan tag priority field over tos ? 1 ? select tos over vlan tag priority field 765 32 0 vp2 vp1 vp0 bit [2:0]: ? priority when the vl an tag priority field is 0 (default 0) bit [5:3]: ? priority when the vl an tag priority field is 1 (default 0) bit [7:6]: ? priority when the vl an tag priority field is 2 (default 0)
MVTX2603 data sheet 51 zarlink semiconductor inc. 13.6.5 avpmm ? vlan priority map ?i 2 c address: h0ae, cpu address: h504 ? accessed by serial interface and i 2 c (r/w) map vlan priority into eigh t level transmit priorities: 13.6.6 avpmh ? vlan priority map ?i 2 c address: h0af, cpu address: h505 ? accessed by serial interface and i 2 c (r/w) map vlan priority into eigh t level transmit priorities: 13.6.7 tospml ? tos priority map ?i 2 c address: h0b0, cpu address: h506 ? accessed by serial interface and i 2 c (r/w) map tos field in ip pa cket into eight level transmit priorities: 7 6 43 10 vp5 vp4 vp3 vp2 bit [0]: ? priority when the vlan tag priority field is 2 (default 0) bit [3:1]: ? priority when the vl an tag priority field is 3 (default 0) bit [6:4]: ? priority when the vl an tag priority field is 4 (default 0) bit [7]: ? priority when the vlan tag priority field is 5 (default 0) 754210 vp7 vp6 vp5 bit [1:0]: ? priority when the vlan tag priority field is 5 (default 0) bit [4:2]: ? priority when the vlan tag priority field is 6 (default 0) bit [7:5]: ? priority when the vlan tag priority field is 7 (default 0) 765 32 0 tp2 tp1 tp0 bit [2:0]: ? priority when the tos field is 0 (default 0) bit [5:3]: ? priority when the tos field is 1 (default 0) bit [7:6]: priority when the tos field is 2 (default 0)
MVTX2603 data sheet 52 zarlink semiconductor inc. 13.6.8 tospmm ? tos priority map ?i 2 c address: h0b1, cpu address: h507 ? accessed by serial interface and i 2 c (r/w) map tos field in ip pa cket into four level transmit priorities: 13.6.9 tospmh ? tos priority map ?i 2 c address: h0b2, cpu address: h508 ? accessed by serial interface and i 2 c (r/w) map tos field in ip pa cket into four level transmit priorities: 13.6.10 avdm ? vlan discard map ?i 2 c address: h0b3, cpu address: h509 ? accessed by serial interface and i 2 c (r/w) map vlan priority into frame discard when low priority buffer usage is above threshold 76 43 10 tp5 tp4 tp3 tp2 bit [0]: ? priority when the tos field is 2 (default 0) bit [3:1]: ? priority when the tos field is 3 (default 0) bit [6:4]: ? priority when the tos field is 4 (default 0) bit [7]: ? priority when the tos field is 5 (default 0) 754210 tp7 tp6 tp5 bit [1:0]: ? priority when the tos field is 5 (default 0) bit [4:2]: ? priority when the tos field is 6 (default 0) bit [7:5]: ? priority when the tos field is 7 (default 0) 7 6 543 2 10 fdv7 fdv6 fdv5 fdv4 fdv3 fdv2 fdv1 fdv0 bit [0]: ? frame drop priority when vlan tag priority field is 0 (default 0) bit [1]: ? frame drop priority when vlan tag priority field is 1 (default 0) bit [2]: ? frame drop priority when vlan tag priority field is 2 (default 0) bit [3]: ? frame drop priority when vlan tag priority field is 3 (default 0)
MVTX2603 data sheet 53 zarlink semiconductor inc. 13.6.11 tosdml ? tos discard map ?i 2 c address: h0b4, cpu address: h50a ? accessed by serial interface and i 2 c (r/w) map tos into frame discard when low priority buffer usage is above threshold 13.6.12 bmrc - broadcast/multicast rate control ?i 2 c address: h0b5, cpu address: h50b ? accessed by serial interface and i 2 c (r/w) ? this broadcast and multicast rate defines for each port the number of packet allowed to be forwarded within a specified time. once the packet rate is reached, packets will be dr opped. to turn off the rate limit, program the field to 0. timebase is based on register 502 [6:4]. bit [4]: ? frame drop priority when vlan tag priority field is 4 (default 0) bit [5]: ? frame drop priority when vlan tag priority field is 5 (default 0) bit [6]: ? frame drop priority when vlan tag priority field is 6 (default 0) bit [7]: ? frame drop priority when vlan tag priority field is 7 (default 0) 7 6 543 2 10 fdt7 fdt6 fdt5 fdt4 fdt3 fdt2 fdt1 fdt0 bit [0]: ? frame drop priority when tos field is 0 (default 0) bit [1]: ? frame drop priority when tos field is 1 (default 0) bit [2]: ? frame drop priority when tos field is 2 (default 0) bit [3]: ? frame drop priority when tos field is 3 (default 0) bit [4]: ? frame drop priority when tos field is 4 (default 0) bit [5]: ? frame drop priority when tos field is 5 (default 0) bit [6]: ? frame drop priority when tos field is 6 (default 0) bit [7]: ? frame drop priority when tos field is 7 (default 0) 7430 broadcast rate multicast rate bit [3:0]: ? multicast rate control number of multicast packets allowed within the time defined in bits 6 to 4 of the flooding control register (fcr). (default 0) . bit [7:4]: ? broadcast rate control number of broadcast packets allowed within the time defined in bits 6 to 4 of the flooding control register (fcr). (default 0)
MVTX2603 data sheet 54 zarlink semiconductor inc. 13.6.13 ucc ? unicast congestion control ?i 2 c address: h0b6, cpu address: h50c ? accessed by serial interface and i 2 c (r/w) 13.6.14 mcc ? multicast congestion control ?i 2 c address: h0b7, cpu address: h50d ? accessed by serial interface and i 2 c (r/w) 13.6.15 pr100 ? port reservation for 10/100 ports ?i 2 c address: h0b8, cpu address: h50e ? accessed by serial interface and i 2 c (r/w) 7 0 unicast congest threshold bit [7:0]: ? number of frame count. used for best effort dropping at b% when destination port?s best effort queue reaches ucc threshold and shared pool is all in use. granularity 1 frame. (default: h10 for 2 mb/bank or h08 for 1 mb/bank) 754 0 fc reaction prd multicast congest threshold bit [4:0]: ? in multiples of two. used for triggering mc flow control when destination multicast port?s best effort queue reaches mcc threshold. (default 0x10) bit [7:5]: ? flow control reaction period (default 2) granularity 4 usec. 7430 buffer low thd sp buffer reservation bit [3:0]: ? per port buffer reservation. ? define the space in the fdb reserved for each 10/100 port. expressed in multiples of 4 packets. for each packet 1536 bytes are reserved in the memory. bits [7:4]: ? expressed in multiples of 4 packets. threshold for dropping all best effort frames when destination port best efforts queues reach ucc threshold and shared pool all used and source port reservation is at or below the pr100[7:4] level. also th e threshold for init iating uc flow control. ?default: ? h36 for 24+2 configuration with memory 2 mb/bank; ? h24 for 24+2 configuration with 1 mb/bank;
MVTX2603 data sheet 55 zarlink semiconductor inc. 13.6.16 prg ? port reservation for giga ports ?i 2 c address: h0b9, cpu address: h50f ? accessed by serial interface and i 2 c (r/w) 13.6.17 sfcb ? share fcb size ?i 2 c address: h0ba, cpu address: h510 ? accessed by serial interface and i 2 c (r/w) 13.6.18 c2rs ? class 2 reserve size ?i 2 c address: h0bb, cpu address: h511 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 2 (third lowest priority). granularity 1. (default 0) 730 buffer low thd sp buffer reservation bit [3:0]: ? per source port buffer reservation. ? define the space in the fdb reserved for each gigabit port. expressed in multiples of 16 packets. for each packet 1536 bytes are reserved in the memory. bits [7:4]: ? expressed in multiples of 16 packets. threshold for dropping all best effort frames when destination port best effort queues reach ucc threshold and shared pool is all used and source port reservation is at or below the prg[7:4] level. also th e threshold for init iating uc flow control. ?default: ? h58 for memory 2 mb/bank; ? h35 for 1 mb/bank; 7 0 shared buffer size bits [7:0]: ? expressed in multiples of 4 packets. buffer reservation for shared pool. ?default: ? h64 for 24+2 configuration with memory of 2 mb/bank; ? h14 for 24+2 configuration with memory of 1 mb/bank; 7 0 class 2 fcb reservation
MVTX2603 data sheet 56 zarlink semiconductor inc. 13.6.19 c3rs ? class 3 reserve size ?i 2 c address: h0bc, cpu address: h512 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 3. granularity 1. (default 0) 13.6.20 c4rs ? class 4 reserve size ?i 2 c address: h0bd, cpu address: h513 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 4. granularity 1. (default 0) 13.6.21 c5rs ? class 5 reserve size ?i 2 c address: h0be; cpu address: h514 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 5. granularity 1. (default 0) 13.6.22 c6rs ? class 6 reserve size ?i 2 c address: h0bf; cpu address h515 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 6 (second highest priority). granularity 1. (default 0) 13.6.23 c7rs ? class 7 reserve size ?i 2 c address: h0c0; cpu address: h516 ? accessed by serial interface and i 2 c (r/w) ? buffer reservation for class 7 (highest priority). granularity 1. (default 0) 7 0 class 3 fcb reservation 7 0 class 4 fcb reservation 7 0 class 5 fcb reservation 7 0 class 6 fcb reservation 7 0 class 7 fcb reservation
MVTX2603 data sheet 57 zarlink semiconductor inc. 13.6.24 classes byte limit set 0 ? accessed by serial interface and i 2 c (r/w) ? c ? qosc00 ? byte_c01 (i 2 c address h0c1, cpu address 517) ? b ? qosc01 ? byte_c02 (i 2 c address h0c2, cpu address 518) ? a ? qosc02 ? byte_c03 (i 2 c address h0c3, cpu address 519) qosc00 through qosc02 represents one set of values a-c for a 10/100 port when using the weighted random early drop (wred) scheme described in chapter 7.7. there ar e four such sets of values a-c specified in classes byte limit set 0, 1, 2 and 3. each 10/ 100 port can choose one of the four byte limit sets as specified by the qos select field located in bits 5 to 4 of the ecr2n register. the values a-c are per-queue byte thresholds for random early drop. qosc02 represents a, and qosc00 represents c. granularity when delay bound is used: qosc02: 128 byte s, qosc01: 256 bytes. qosc00: 512 bytes. granularity when wfq is used: qosc02: 512 bytes, qosc01: 512 bytes, qosc00: 512 bytes. 13.6.25 classes byte limit set 1 ? accessed by serial interface and i 2 c (r/w) c - qosc03 ? byte_c11 (i 2 c address h0c4, cpu address 51a) b - qosc04 ? byte_c12 (i 2 c address h0c5, cpu address 51b) a - qosc05 ? byte_c13 (i 2 c address h0c6, cpu address 51c) qosc03 through qosc05 represents one set of values a-c for a 10/100 port when using the weighted random early detect (wred) scheme. granularity when delay bound is used: qosc05: 128 byte s, qosc04: 256 bytes. qosc03: 512 bytes. granularity when wfq is used: qosc05: 512 bytes, qosc04: 512 bytes, qosc03: 512 bytes. 13.6.26 classes byte limit set 2 ? accessed by serial interface and i 2 c (r/w) c - qosc06 ? byte_c21 (cpu address 51d) b - qosc07 ? byte_c22 (cpu address 51e) a - qosc08 ? byte_c23 (cpu address 51f) qosc06 through qosc08 represents one set of values a-c for a 10/100 port when using the weighted random early detect (wred) scheme. granularity when delay bound is used: qosc08: 128 byte s, qosc07: 256 bytes. qosc06: 512 bytes. granularity when wfq is used: qosc08: 512 bytes, qosc07: 512 bytes, qosc06: 512 bytes. 13.6.27 classes byte limit set 3 ? accessed by serial interface and i 2 c (r/w) c - qosc09 ? byte_c31 (cpu address 520) b - qosc10 ? byte_c32 (cpu address 521) a - qosc11 ? byte_c33 (cpu address 522) qosc09 through qosc011 represents one set of values a-c for a 10/100 port when using the weighted random early detect (wred) scheme.
MVTX2603 data sheet 58 zarlink semiconductor inc. granularity when delay bound is used: qosc11: 128 byte s, qosc10: 256 bytes. qosc09: 512 bytes. granularity when wfq is used: qosc11: 512 bytes, qosc10: 512 bytes, qosc09: 512 bytes. 13.6.28 classes byte limit giga port 1 ? accessed by serial interface and i 2 c (r/w) f - qosc12 ? byte_c2_g1 (i 2 c address h0c7, cpu address 523) e - qosc13 ? byte_c3_g1 (i 2 c address h0c8, cpu address 524) d - qosc14 ? byte_c4_g1 (i 2 c address h0c9, cpu address 525) c - qosc15 ? byte_c5_g1 (i 2 c address h0ca, cpu address 526) b - qosc16 ? byte_c6_g1 (i 2 c address h0cb, cpu address 527) a - qosc17 ? byte_c7_g1 (i 2 c address h0cc, cpu address 528) qosc12 through qosc17 represent the values a-f for gigabit port 24. they are per-queue byte thresholds for random early drop. qosc17 represents a, and qosc12 represents f. granularity when delay bound is used: qosc17 and qosc16: 256 bytes, qosc15 and qosc14: 512 bytes, qosc13 and qosc12: 1024 bytes. granularity when wfq is used: qosc17 to qosc12: 1024 bytes 13.6.29 classes byte limit giga port 2 ? accessed by serial interface and i 2 c (r/w) f - qosc18 ? byte_c2_g2 (i 2 c address h0cd, cpu address 529) e - qosc19 ? byte_c3_g2 (i 2 c address h0ce, cpu address 52a) d - qosc20 ? byte_c4_g2 (i 2 c address h0cf, cpu address 52b) c - qosc21 ? byte_c5_g2 (i 2 c address h0d0, cpu address 52c) b - qosc22 ? byte_c6_g2 (i 2 c address h0d1, cpu address 52d) a - qosc23 ? byte_c7_g2 (i 2 c address h0d2, cpu address 52e) qosc18 through qosc23 represent the values a-f for gigabit port 2. they are per-queue byte thresholds for random early drop. qosc23 represents a, and qosc18 represents f. granularity when delay bound is used: qosc23 and qosc22: 256 bytes, qosc21 and qosc20: 512 bytes, qosc19 and qosc18: 1024 bytes. granularity when wfq is used: qosc18 to qosc23: 1024 bytes 13.6.30 classes wfq credit set 0 ? accessed by serial interface (r/w) w0 - qosc24[5:0] ? credit _c00 (cpu address 52f) w1 - qosc25[5:0] ? credit _c01 (cpu address 530) w2 - qosc26[5:0] ? credit _c02 (cpu address 531) w3 - qosc27[5:0] ? credit _c03 (cpu address 532)
MVTX2603 data sheet 59 zarlink semiconductor inc. qosc24 through qosc27 represents one set of wfq parameters for a 10/100 port. there are four such sets of values. the granularity of the numbers is 1 and their sum must be 64. qosc27 corresponds to w3 and qosc24 corresponds to w0. ? qosc24[7:6]: priority service type for the ports select th is parameter set. option 1 to 4 ? qosc25[7]: priority service allow flow cont rol for the ports select this parameter set ? qosc25[6]: flow control p ause best effort traffic only both flow control allow and flow control best effort only can take effect only the priority type is wfq. 13.6.31 classes wfq credit set 1 ? accessed by serial interface (r/w) w0 - qosc28[5:0] ? credit _c10 (cpu address 533) w1 - qosc29[5:0] ? credit _c11 (cpu address 534) w2 - qosc30[5:0] ? credit _c12 (cpu address 535) w3 - qosc31[5:0] ? credit _c13 (cpu address 536) qosc28 through qosc31 represents one set of wfq parameters for a 10/100 port. there are four such sets of values. the granularity of the numbers is 1 and their sum must be 64. qosc31 corresponds to w3 and qosc28 corresponds to w0. qosc28[7:6]: priority service ty pe for the ports sele ct this parameter set. option 1 to 4 qosc29[7]: priority service al low flow control for the port s select this parameter set qosc29[6]: flow control paus e best effort traffic only 13.6.32 classes wfq credit set 2 ? accessed by serial interface (r/w) w0 - qosc32[5:0] ? credit _c20 (cpu address 537) w1 - qosc33[5:0] ? credit _c21 (cpu address 538) w2 - qosc34[5:0] ? credit _c22 (cpu address 539) w3 - qosc35[5:0] ? credit _c23 (cpu address 53a) qosc35 through qosc32 represents one set of wfq parameters for a 10/100 port. there are four such sets of values. the granularity of the numbers is 1 and their sum must be 64. qosc35 corresponds to w3 and qosc32 corresponds to w0. ? qosc32[7:6]: priority se rvice type for the ports select this parameter set. option 1 to option 4 ? qosc33[7]: priority service allow flow cont rol for the ports select this parameter set ? qosc33[6]: flow control pause best effort traffic only 13.6.33 classes wfq credit set 3 ? accessed by serial interface (r/w) w0 - qosc36[5;0] ? credit _c30 (cpu address 53b) w1 - qosc37[5:0] ? credit _c31 (cpu address 53c) w2 - qosc38[5:0] ? credit _c32 (cpu address 53d) w3 - qosc39[5:0] ? credit _c33 (cpu address 53e)
MVTX2603 data sheet 60 zarlink semiconductor inc. qosc39 through qosc36 represents one set of wfq parameters for a 10/100 port. there are four such sets of values. the granularity of the numbers is 1, and thei r sum must be 64. qosc39 co rresponds to w3 and qosc36 corresponds to w0. ? qosc36[7:6]: priority se rvice type for the ports select this parameter set. option 1 to option 4 ? qosc37[7]: priority service allow flow cont rol for the ports select this parameter set ? qosc37[6]: flow control pause best effort traffic only 13.6.34 classes wfq credit port g1 ? accessed by serial interface (r/w) w0 - qosc40[5:0] ? credit _c0_g1 (cpu address 53f) [7:6] - priority servic e type. option 1 to 4. w1 - qosc41[5:0] ? credit _c1_g1 (cpu address 540) [7]: priority service allow flow control for the ports select this parameter set. [6]: flow control pause best effort traffic only w2 - qosc42[5:0] ? credit _c2_g1 (cpu address 541) w3 - qosc43[5:0] ? credit _c3_g1 (cpu address 542) w4 - qosc44[5:0] ? credit _c4_g1 (cpu address 543) w5 - qosc45[5:0] ? credit _c5_g1 (cpu address 544) w6 - qosc46[5:0] ? credit _c6_g1 (cpu address 545) w7 - qosc47[5:0] ? credit _c7_g1 (cpu address 546) qosc40 through qosc47 represents the set of wfq parame ters for gigabit port 24. the granularity of the numbers is 1 and their sum must be 64. qosc47 corresponds to w7 and qosc40 corresponds to w0. in the 2g trunk configuration, the sum of all valu es qosc40 through qosc47 must equal 128. 13.6.35 classes wfq credit port g2 ? accessed by serial interface (r/w) w0 - qosc48[5:0] ? credit _c0_g2 (cpu address 547) [7:6] - priority servic e type. option 1 to 4. w1 - qosc49[5:0] ? credit _c1_g2 (cpu address 548) [7]: priority service allow flow control for the ports select this parameter set. [6]: flow control pause best effort traffic only w2 - qosc50[5:0] ? credit _c2_g2 (cpu address 549) w3 - qosc51[5:0] ? credit _c3_g2 (cpu address 54a) w4 - qosc52[5:0] ? credit _c4_g2 (cpu address 54b) w5 - qosc53[5:0] ? credit _c5_g2 (cpu address 54c) w6 - qosc54[5:0] ? credit _c6_g2 (cpu address 54d) w7 - qosc55[5:0] ? credit _c7_g2 (cpu address 54e) qosc48 through qosc55 represents the set of wfq parame ters for gigabit port 25. the granularity of the numbers is 1, and their sum must be 64. qosc55 corresponds to w7 and qosc48 corresponds to w0. in the 2g trunk configuration, the sum of all valu es qosc48 through qosc55 must equal 128.
MVTX2603 data sheet 61 zarlink semiconductor inc. 13.6.36 class 6 shaper control port g1 ? accessed by serial interface (r/w) ? qosc56[5:0] ? token_rate_g1 (address 54f). programs the average rate for gigabit port 1. when equal to 0, shaper is disable. granularity is 1. ? qosc57[7:0] ? token_limit_g1 (addr ess 550). programs the maximum counter for gigabit port1. granularity is 16 bytes. shaper is implemented to control the peak and average rate for outgoing traffic with priority 6 (queue 6). shaper is limited to gigabit ports and queue p6 when it is in strict priority. qosc41 programs the peak rate for gigabit port 1. see programming qos registers applic ation note for more information. 13.6.37 class 6 shaper control port g2 ? accessed by serial interface (r/w) ? qosc58[5:0] ? token_rate_g2 (cpu address 551). programs t he average rate for gigabit port 2. when equal to 0, shaper is disabl e. granularity is 1. ? qosc59[7:0] ? token_limit_g2 (c pu address 552). programs the maximum counter for gigabit port2. granularity is 16 bytes. shaper is implemented to control the peak and average rate for outgoing traffic with priority 6 (queue 6). shaper is limited to gigabit ports and queue p6 when it is in strict priority. qosc49 programs the peak rate for gigabit port 2. see programming qos registers applic ation note for more information. 13.6.38 rdrc0 ? wred rate control 0 ?i 2 c address: h0fb, cpu address: h553 ? accessed by serial interface and i c c (r/w) 13.6.39 rdrc1 ? wred rate control 1 ?i 2 c address: h0fc, cpu address: h554 ? accessed by serial interface and i 2 c (r/w) 7430 x rate y rate bits [7:4]: ? corresponds to the frame drop percentage x% for wred. granularity 6.25%. bits [3:0]: ? corresponds to the frame drop percentage y% for wred. granularity 6.25%. see programming qos registers application note for more information. 7430 z rate b rate bits [7:4]: ? corresponds to the frame drop percentage z% for wred. granularity 6.25%. bits [3:0]: ? corresponds to the best effort frame drop percentage b%, when shared pool is all in use and destination port best effort queue reaches ucc. granularity 6.25%. see programming qos register applic ation note for mo re information.
MVTX2603 data sheet 62 zarlink semiconductor inc. 13.6.40 user defined logical ports and well known ports the MVTX2603 supports classifying packet priority through layer 4 logical port information. it can be setup by 8 well known ports, 8 user defined logical ports and 1 user defined range. the 8 well known ports supported are ?0:23 ?1:512 ?2:6000 ?3:443 ?4:111 ? 5:22555 ?6:22 ?7:554 their respective priority can be programmed via well_kno wn_port [7:0] priority register. well_known_port_ enable can individually turn on/off each well known port if desired. similarly, the user defined logical port provides the user programmability to the priority, plus the flexibility to select specific logical ports to fit the applications. the 8 user logical ports can be programmed via user_port 0-7 registers. two registers are required to be programmed fo r the logical port number. the respective priority can be programmed to the user_port [7:0] priority register. the port priority can be individually enabled/disabled via user_port_enable register. the user defined range provides a range of logical port numbers with the same priority level. programming is similar to the user defined logical port. instead of programming a fixed port number, an upper and lower limit need to be programmed, they are: {rhighh, rhighl} and {rlowh , rlowl} respectively. if the value in the upper limit is smaller or equal to the lower limit, the function is disabled. any ip packet with a logical port that is less than the upper limit and more than the lower limit will use the priority specified in rpriority. 13.6.40.1 user_port0_(0~7) ? user define logical port (0~7) ? user_port_0 - i 2 c address h0d6 + 0de; cpu address 580(low) + 581(high) ? user_port_1 - i 2 c address h0d7 + 0df; cpu address 582 + 583 ? user_port_2 - i 2 c address h0d8 + 0e0; cpu address 584 + 585 ? user_port_3 - i 2 c address h0d9 + 0e1; cpu address 586 + 587 ? user_port_4 - i 2 c address h0da + 0e2; cpu address 588 + 589 ? user_port_5 - i 2 c address h0db + 0e3; cpu address 58a + 58b ? user_port_6 - i 2 c address h0dc + 0e4; cpu address 58c + 58d ? user_port_7 - i 2 c address h0dd + 0e5; cpu address 58e + 58f ? accessed by serial interface and i 2 c (r/w) ? (default 00) this register is duplicated eight times fr om port 0 through port 7 and allows the definition of eight separate ports. 70 tcp/udp logic port low 70 tcp/udp logic port high
MVTX2603 data sheet 63 zarlink semiconductor inc. 13.6.40.2 user_port_[1:0]_priority - u ser define logic port 1 and 0 priority ?i 2 c address: h0e6, cpu address: h590 ? accessed by serial interface and i 2 c (r/w) ? the chip allows the definition of the priority 13.6.40.3 user_port_[3:2]_priority - u ser define logic port 3 and 2 priority ?i 2 c address: h0e7, cpu address: h591 ? accessed by serial interface and i 2 c (r/w) 13.6.40.4 user_port_[5:4]_priority - u ser define logic port 5 and 4 priority ?i 2 c address: h0e8, cpu address: h592 ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.5 user_port_[7:6]_priority - u ser define logic port 7 and 6 priority ?i 2 c address: h0e9, cpu address: h593 ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.6 user_port_enable [7:0] ? u ser define logic 7 to 0 port enables ?i 2 c address: h0ea, cpu address: h594 ? accessed by serial interface and i 2 c (r/w) ? (default 00) 7543 10 priority 1 drop priority 0 drop bits [3:0]: ? priority setting, transmission + dropping, for logic port 0 bits [7:4]: ? priority setting, transmission + dropping, for logic port 1 (default 00) 754310 priority 3 drop priority 2 drop 754310 priority 5 drop priority 4 drop 754310 priority 7 drop priority 6 drop 765 4 3 2 1 0 p7 p6 p5 p4 p3 p2 p1 p0
MVTX2603 data sheet 64 zarlink semiconductor inc. 13.6.40.7 well_known_port [1:0] priority - well known logic port 1 and 0 priority ?i 2 c address: h0eb, cpu address: h595 ? accessed by serial interface and i 2 c (r/w) ? priority 0 - well known port 23 for telnet applications ? priority 1 - well known port 512 for tcp/udp ? (default 00) 13.6.40.8 well_known_port [3:2] priority - well known logic port 3 and 2 priority ?i 2 c address: h0ec, cpu address: h596 ? accessed by serial interface and i 2 c (r/w) ? priority 2 - well known port 6000 for xwin. ? priority 3 - well known port 443 for http. sec ? (default 00) 13.6.40.9 well_known_port [5:4] priority - well known logic port 5 and 4 priority ?i 2 c address: h0ed, cpu address: h597 ? accessed by serial interface and i 2 c (r/w) ? priority 4 - well known port 111 for sun rpe. ? priority 5 - well known port 22555 for ip phone call setup ? (default 00) 13.6.40.10 well_known_port [7:6] priority - well known logic port 7 and 6 priority ?i 2 c address: h0ee, cpu address: h598 ? accessed by serial interface and i 2 c (r/w) ? priority 6 - well known port 22 for ssh. ? priority 7 - well known port 554 for rtsp. ? (default 00) 7543 10 priority 1 drop priority 0 drop 754310 priority 3 drop priority 2 drop 754310 priority 5 drop priority 4 drop 754310 priority 7 drop priority 6 drop
MVTX2603 data sheet 65 zarlink semiconductor inc. 13.6.40.11 well known_port_enable [7:0] ? well known logic 7 to 0 port enables ?i 2 c address: h0ef, cpu address: h599 ? accessed by serial interface and i 2 c (r/w) ? 1 - enable ? 0 - disable ? (default 00) 13.6.40.12 rlowl ? user define range low bit 7:0 ?i 2 c address: h0f4, cpu address: h59a ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.13 rlowh ? user define range low bit 15:8 ?i 2 c address: h0f5, cpu address: h59b ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.14 rhighl ? user define range high bit 7:0 ?i 2 c address: h0d3, cpu address: h59c ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.15 rhighh ? user define range high bit 15:8 ?i 2 c address: h0d4, cpu address: h59d ? accessed by serial interface and i 2 c (r/w) ? (default 00) 13.6.40.16 rpriority ? user define range priority ?i 2 c address: h0d5, cpu address: h59e ? accessed by serial interface and i 2 c (r/w) ? rlow and rhigh form a range for logi cal ports to be classified with priority specified in rpriority 765 4 3 2 1 0 p7 p6 p5 p4 p3 p2 p1 p0 743 10 range transmit priority drop bit [3:1] ? transmit priority bits [0]: ? drop priority
MVTX2603 data sheet 66 zarlink semiconductor inc. 13.7 group 6 address misc group 13.7.1 mii_op0 ? mii register option 0 ?i 2 c address: hf0, cpu address:h600 ? accessed by serial interface and i 2 c (r/w) 13.7.2 mii_op1 ? mii register option 1 ?i 2 c address: hf1, cpu address:h601 ? accessed by serial interface and i 2 c (r/w) 13.7.3 fen ? feature register ?i 2 c address: hf2, cpu address: h602 ? accessed by serial interface and i 2 c (r/w) 76 5 4 0 hfc 1prst disj vendor spc. reg addr bits [7]: ? half duplex flow control feature ? 0 = half duplex flow control always enable ? 1 = half duplex flow control by negotiation bits [6]: ? link partner reset auto-negotiate disable bits [5]: ? disable jabber detection. this is for homepna application or any serial operation slower than 10 mbps. ? 1 = disable ? 0 = enable bit [4:0]: ? vendor specified link status register address (null value means don?t use it) (default 00); used when the linkup bit position in the phy is non-standard. 743 0 speed bit location duplex bit location bits [3:0]: ? duplex bit location in vendor specified register bits [7:4]: ? speed bit location in vendor specified register ? (default 00) 765 3 21 0 dml mii ds bits [1:0]: ? reserved (default 0)
MVTX2603 data sheet 67 zarlink semiconductor inc. 13.7.4 miic0 ? mii command register 0 ? cpu address: h603 ? accessed by serial in terface only (r/w) ? bit [7:0] mii data [7:0] note: before programming mii command: set fen[6], check miic3, making sure no rdy and no valid; then program mii command. 13.7.5 miic1 ? mii command register 1 ? cpu address: h604 ? accessed by serial in terface only (r/w) ? bit [7:0] mii data [15:8] note : before programming mii command: set fen[6], check miic3, making sure no rdy and no valid; then program mii command. 13.7.6 miic2 ? mii command register 2 ? cpu address :h605 ? accessed by serial in terface only (r/w) note : before programming mii command: set fen[6], check miic3, making sure no rdy and no valid; then program mii command. writing to this register will initiate a serial management cycl e to the mii management interface. for detail information, please refer to the phy control application note. bit [2]: ? support ds ef code. (default 0) ? when 101110 is detected in ds field (tos [7:2]), the frame priority is set for 110 and drop is set for 0 bit [5:3]: ? reserved (default 010) bit [6]: ? disable mii management state machine ? 0: enable mii management state machine (default 0) ? 1: disable mii management state machine bit [7]: ? disable using mct link list structure ? 0: enable using mct link list structure (default 0) ? 1: disable using mct link list structure 76 54 0 mii op register address bits [4:0]: ? reg_ad ? register phy address bit [6:5] ? op ? operation code ?10? for read command and ?01? for write command
MVTX2603 data sheet 68 zarlink semiconductor inc. 13.7.7 miic3 ? mii command register 3 ? cpu address: h606 ? accessed by serial in terface only (r/w) note : before programming mii command: set fen[6], check miic3, making sure no rdy and no valid; then program mii command. 13.7.8 miid0 ? mii data register 0 ? cpu address: h607 ? accessed by serial interface only (ro) ? bit [7:0] mii data [7:0] 13.7.9 miid1 ? mii data register 1 ? cpu address: h608 ? accessed by serial interface only (ro) ? bit [7:0] mii data [15:8] 13.7.10 led mode ? led control ? cpu address: h609 ? accessed by serial interface and i 2 c (r/w) 7654 0 rdy valid phy address bits [4:0]: ? phy_ad ? 5 bit phy address bit [6] ? valid ? data valid from phy (read only) bit [7] ? rdy ? data is retu rned from phy (ready only) 7543210 clock rate hold time bit [0] ? reserved (default 0) bit [2:1]: ? hold time for led signal (default= 00) ? 00=8msec 01=16msec 10=32msec 11=64msec bit [4:3]: ? led clock frequency (default 0) for 100mhz sclk 00 = 100 m/8 = 12.5 mhz 01 = 100 m/16 = 6.25 mhz 10 = 100 m/32 = 3.125 mhz 11 = 100 m/64 = 1.5625 mhz for 125 mhz sclk 00 = 125 m/64 = 1953 khz 01 = 125 m/128 = 977 khz 10 = 125m/512=244 khz 11 = 125 m/1024 = 122 khz bit [7:6]: ? reserved. must be 0. (default 0)
MVTX2603 data sheet 69 zarlink semiconductor inc. 13.7.11 checksum - eeprom checksum ?i 2 c address: ff, cpu address: h60b ? accessed by serial interface and i 2 c (r/w) before requesting that t he MVTX2603 updates the eeprom device, the correct checksum needs to be calculated and written into this checksum register. when the mv tx2603 boots from the eeprom the checksum is calculated and the value must be zero. if the checksum is not zeroed the MVTX2603 does not start and pi n checksum_ok is set to zero. the checksum formula is:ff i 2 c register = 0 i=0 13.8 group 7 address port mirroring group 13.8.1 mirror1_src ? port mirror source port ? cpu address: h700 ? accessed by serial interface (r/w) (default 7f) 13.8.2 mirror1_dest ? port mirror destination ? cpu address: h701 ? accessed by serial interface (r/w) (default 17) bit [7:0]: ? (default 0) 76 5 4 0 i/o src port select bit [4:0]: ? source port to be mirrored. use illegal port number to disable mirroring bit [5]: ? 1 ? select ingress data ? 0 ? select egress data bit [7]: ? must be ?1? 754 0 dest port select bit [4:0]: ? port mirror destination
MVTX2603 data sheet 70 zarlink semiconductor inc. 13.8.3 mirror2_src ? port mirror source port ? cpu address: h702 ? accessed by serial interface (r/w) (default ff) 13.8.4 mirror2_dest ? port mirror destination ? cpu address: h703 ? accessed by serial interface (r/w) (default 00) 13.9 group f address cpu access group 13.9.1 gcr-global control register ? cpu address: hf00 ? accessed by serial interface. (r/w) 7654 0 i/o src port select bit [4:0]: ? source port to be mirrored. use illegal port number to disable mirroring bit [5]: ? 1 ? select ingress data ? 0 ? select egress data bit [7] ? must be 1 754 0 dest port select bit [4:0]: ? port mirror destination 743210 reset bist sr sc bit [0]: ? store configuration (default = 0) ? write ?1? followed by ?0? to store configurat ion into external eeprom bit [1]: ? store configuration and reset (default = 0) ? write ?1? to store configuration in to external eepr om and reset chip bit [2]: ? start bist (default = 0) ? write ?1? followed by ?0? to start the device?s built-in self-test. the result is found in the dcr register. bit [3]: ? soft reset (default = 0) ? write ?1? to reset chip bit [7:4]: ? reserved.
MVTX2603 data sheet 71 zarlink semiconductor inc. 13.9.2 dcr-device status and signature register ? cpu address: hf01 ? accessed by serial interface. (ro) 13.9.3 dcr1-giga port status ? cpu address: hf02 ? accessed by serial interface (ro) 76543210 revision signature re binp br bw bit [0]: ? 1: busy writing configuration to i 2 c ? 0: not busy writing configuration to i 2 c bit [1]: ? 1: busy reading configuration from i 2 c ? 0: not busy reading configuration from i 2 c bit [2]: ? 1: bist in progress ? 0: bist not running bit [3]: ? 1: ram error ? 0: ram ok bit [5:4]: ? device signature ? 01: MVTX2603 device bit [7:6]: ? revision ? 00: initial silicon ? 01: xa1 silicon 76 43 2 1 0 cic giga1 giga0 bit [1:0]: ? giga port 0 strap option ? 00 ? 100 mb mii mode ? 01 ? 2 g mode ? 10 ? gmii ?11 ? pcs bit [3:2] ? giga port 1 strap option ? 00 ? 100 mb mii mode ? 01 ? 2 g mode ? 10 ? gmii ?11 ? pcs bit [7] ? chip initialization completed
MVTX2603 data sheet 72 zarlink semiconductor inc. 13.9.4 dpst ? device port status register ? cpu address: hf03 ? accessed by serial interface (r/w) 13.9.5 dtst ? data read back register ? cpu address: hf04 ? accessed by serial interface (ro) ? this register provides various internal information as selected in dpst bit [4:0 ]. refer to the phy control application note. when bit is 1 ? bit [0] ? flow control enable ? bit [1] ? full duplex port ? bit [2] ? fast ethernet port (if not gigabit port) ? bit [3] ? link is down ? bit [4] ? giga port bit[4:0]: ? read back index register. this is used for selecting what to read back from dtst. (default 00) - 5?b00000 - port 0 operating mode and negotiation status - 5?b00001 - port 1 operating mode/neg status - 5?b00010 - port 2 operating mode/neg status - 5?b00011 - port 3 operating mode/neg status - 5?b00100 - port 4 operating mode/neg status - 5?b00101 - port 5 operating mode/neg status - 5?b00110 - port 6 operating mode/neg status - 5?b00111 - port 7 operating mode/neg status - 5?b01000 - port 8 operating mode/neg status - 5?b01001 - port 9 operating mode/neg status - 5?b01010 - port 10 operating mode/neg status - 5?b01011 - port 11 operating mode/neg status - 5?b01100 - port 12 operating mode/neg status - 5?b01101 - port 13 operating mode/neg status - 5?b01110 - port 14 operating mode/neg status - 5?b01111 - port 15 operating m ode/neg status - 5?b10000 - port 16 operating mode/neg status - 5?b10001 - port 17 operating mode/neg status - 5?b10010 - port 18 operating mode/neg status - 5?b00011 - port 19 operating mode/neg status - 5?b10100 - port 20 operating mode/neg status - 5?b10101 - port 21 operating mode/neg status - 5?b10110 - port 22 operating mode/neg status - 5?b10111 - port 23 operating mode/neg status - 5?b11000 - reserved - 5?b11001 - port 25 operating m ode/neg status (gigabit port 1) - 5?b11010 - port 26 operating m ode/neg status (gigabit port 2) 76543210 md info sig giga inkdn fe fdpx fcen
MVTX2603 data sheet 73 zarlink semiconductor inc. ? bit [5] ? signal detect (when pcs interface mode) ? bit [6] ? 2 g signal de tect (2 g mode only) ? bit [7] ? module detected (for hot swap purpose) 13.9.6 pllcr - pll control register ? cpu address: hf05 ? accessed by serial interface (rw) bit [3] must be '1' bit [7] selects strap option or lclk/oeclk registers 0 - strap option (default) 1 - lclk/oeclk registers 13.9.7 lclk - la_clk delay from internal oe_clk ? cpu address: hf06 ? accessed by serial interface (rw) pd[12:10] lclk delay 000b 80h 8 buffers delay 001b 40h 7 buffers delay 010b 20h 6 buffers delay 011b 10h 5 buffers delay (recommend) 100b 08h 4 buffers delay 101b 04h 3 buffers delay 110b 02h 2 buffers delay 111b 01h 1 buffers delay the lclk delay from sclk is the sum of the delay programmed in here and the delay in oeclk register. 13.9.8 oeclk - internal oe_clk delay from sclk ? cpu address: hf07 ? accessed by serial interface (rw) the oe_clk is used for generating the oe0 and oe1 signals. pd[15:13] oeclk delay 000b 80h 8 buffers delay 001b 40h 7 buffers delay (recommend) 010b 20h 6 buffers delay 011b 10h 5 buffers delay 100b 08h 4 buffers delay
MVTX2603 data sheet 74 zarlink semiconductor inc. 101b 04h 3 buffers delay 110b 02h 2 buffers delay 111b 01h 1 buffers delay 13.9.9 da ? da register ? cpu address: hfff ? accessed by cpu and se rial interface (ro) ? always return 8?h da . indicate the serial port connection is good. 13.10 tbi registers two sets of tbi registers are used for configure the two gi gabit ports if they are operating in tbi mode. these tbi registers are located inside the switching chip and they are accessed through the mii command and mii data registers. 13.10.1 control register ? mii address: h00 ? read/write bit [15] reset pcs logic and all tbi registers 1 = reset 0 = normal operation bit [14] reserved. must be programmed with ?0?. bit [13] speed selection (see bit 6 for complete details) bit [12] ? auto negotiation enable ? 1 = enable auto-negotiation process ? 0 = disable auto-negotiation process (default) bit [11:10] ? reserved. must be programmed with ?0? bit [9] ? restart auto negotiation ? 1 = restart auto-negotiation process ? 0 = normal operation (default) bit [8:7] ? reserved bit [6] ? speed selection - bit [6][13] - 1 1 = reserved - 0 =1000 mb/s (default) - 1 = 100 mb/s - 0 0 = 10 mb/s bit [5:0] ? reserved. must be programmed with ?0?.
MVTX2603 data sheet 75 zarlink semiconductor inc. 13.10.2 status register ? mii address: h01 ? read only 13.10.3 advertisement register ? mii address: h04 ? read/write bit [15:9] reserved. always read back as ?0?. bit [8] reserved. always read back as ?1?. bit [7:6] reserved. always read back as ?0?. bit [5] ? auto-negotiation complete ? 1 = auto-negotiation process completed ? 0 = auto-negotiation process not completed bit [4] ? reserved. always read back as ?0? bit [3] ? reserved. always read back as ?1? bit [2] ? link status ? 1 = link is up. ? 0 = link is down. bit [1] ? reserved. always read back as ?0?. bit [0] ? reserved. always read back as ?1? bit [15] next page 1 = has next page capabilities. 0 = do not has next page capabilities (default) bit [14] reserved. always read back as ?0?. read only bit [13:12] remote fault. default is ?0?. bit [11:9] ? reserved. always read back as ?0?. read only. bit [8:7] ? pause. default is ?00? bit [6] ? half duplex ? 1 = support half duplex (default) ? 0 = do not support half duplex bit [5] ? full duplex ? 1 = support full duplex (default) ? 0 = do not sup port full duplex bit [4:0] ? reserved. always read back as ?0?. read only.
MVTX2603 data sheet 76 zarlink semiconductor inc. 13.10.4 link partner ability register ? mii address: h05 ? read only 13.10.5 expansion register ? mii address: h06 ? read only 13.10.6 extended status register ? mii address: h15 ? read only bit [15] next page 1 = has next page capabilities 0 = do not has next page capabilities bit [14] acknowledge bit [13:12] remote fault. bit [11:9] ? reserved. always read back as ?0? bit [8:7] ? pause bit [6] ? half duplex ? 1 = support half duplex ? 0 = do not support half duplex bit [5] ? full duplex ? 1 = support full duplex ? 0 = do not sup port full duplex bit [4:0] ? reserved. always read back as ?0? bit [15:2] ? reserved. always read back as ?0? bit [1] ? page received ? 1 = a new page has been received ? 0 = a new page has not been received bit [0] ? reserved. always read back as ?0? bit [15] ? 1000 full duplex ? 1 = support 1000 full duplex operation (default) ? 0 = do not support 1000 full duplex operation bit [14] ? 1000 half duplex ? 1 = support 1000 half duplex operation (default) ? 0 = do not support 1000 half duplex operation bit [13:0] ? reserved. always read back as ?0?
MVTX2603 data sheet 77 zarlink semiconductor inc. 14.0 bga and ball signal descriptions 14.1 bga views (top-view) 14.1.1 encapsulated view 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 a la_d 4 la_d 7 la_d 10 la_d 13 la_d 15 la_a 4 la_o e0_ la_a 8 la_a 13 la_a 16 la_a 19 la_d 33 la_d 36 la_d 39 la_d 42 la_d 45 oe_c lk0 la_c lk0 trun k1 mirr or4 mirr or1 scl sda stro be tsto ut7 b la_d 1 la_d 3 la_d 6 la_d 9 la_d 12 la_d 14 la_a dsc_ la_o e1_ la_a 7 la_a 12 la_a 15 la_a 18 la_d 32 la_d 35 la_d 38 la_d 41 la_d 44 oe_c lk1 la_c lk1 la_d 62 mirr or5 mirr or2 trun k2 rese rved d0 tsto ut8 tsto ut3 c la_c lk la_d 0 la_d 2 la_d 5 la_d 8 la_d 11 la_a 3 la_o e_ la_w e_ t_mo de1 la_a 11 la_a 14 la_a 17 la_a 20 la_d 34 la_d 37 la_d 40 la_d 43 oe_c lk2 la_c lk2 p_d trun k0 mirr or3 mirr or0 auto fd tsto ut11 tsto ut9 tsto ut4 tsto ut0 d agn d la_d 17 la_d 19 la_d 21 la_d 23 la_d 25 la_d 27 la_d 29 la_d 31 la_a 6 la_a 10 la_w e0_ la_d 49 la_d 51 la_d 53 la_d 55 la_d 57 la_d 59 la_d 61 la_d 63 la_d 47 scan col scan clk tsto ut14 tsto ut13 tsto ut12 tsto ut10 tsto ut5 tsto ut1 e sclk la_d 16 la_d 18 la_d 20 la_d 22 la_d 24 la_d 26 la_d 28 la_d 30 la_a 5 la_a 9 la_w e1_ la_d 48 la_d 50 la_d 52 la_d 54 la_d 56 la_d 58 la_d 60 rese rved la_d 46 scan link tsto ut15 m26_ crs m26_ txer scan mod e tsto ut6 tsto ut2 f avc c resi n_ scan en lb_d 63 lb_d 62 vcc vcc vcc vcc vcc m26_ txcl k m26_ txen m26_ mtx clk m26_ rxd v m26_ rxcl k g lb_c lk rese tout _ lb_d 47 lb_d 61 lb_d 60 m26_ txd1 4 m26_ txd1 5 m26_ rxd1 5 m26_ rxer m26_ col h lb_d 46 lb_d 45 lb_d 44 lb_d 59 lb_d 58 m26_ txd1 2 m26_ txd1 3 m26_ rxd1 2 m26_ rxd1 3 m26_ rxd1 4 j lb_d 43 lb_d 42 lb_d 41 lb_d 57 lb_d 56 m26_ txd1 0 m26_ txd1 1 m26_ rxd9 m26_ rxd1 0 m26_ rxd1 1 k lb_d 40 lb_d 39 lb_d 38 lb_d 55 lb_d 54 vdd vdd vdd vdd m26_ txd9 m26_ txd8 m26_ rxd6 m26_ rxd7 m26_ rxd8 l lb_d 37 lb_d 36 lb_d 35 lb_d 53 lb_d 52 m26_ txd4 m26_ txd6 m26_ rxd3 m26_ rxd4 m26_ rxd5 m lb_d 34 lb_d 33 lb_d 32 lb_d 51 lb_d 50 vdd vss vss vss vss vss vss vss vdd m26_ txd7 m26_ txd5 m26_ rxd0 m26_ rxd1 m26_ rxd2 n lb_a 18 lb_a 19 lb_a 20 lb_d 49 lb_d 48 vcc vdd vss vss vss vss vss vss vss vdd vcc m26_ txd2 m26_ txd3 gref _clk 1 p lb_a 15 lb_a 16 lb_a 17 lb_w e0_ lb_ we1_ vcc vss vss vss vss vss vss vss vcc m26_ txd0 m26_ txd1 mdio gref _clk 0 r lb_a 10 lb_a 11 lb_a 12 lb_a 13 lb_a 14 vcc vss vss vss vss vss vss vss vcc m25_ crs m25_ txer mdc m_cl k t lb_a 5 lb_a 6 lb_a 7 lb_a 8 lb_a 9 vcc vss vss vss vss vss vss vss vcc m25_ txcl k m25_ txen m25_ mtx clk m25_ rxd v m25_ rxcl k u lb_o e0_ lb_o e1_ t_mo de0 lb_d 31 lb_d 30 vcc vdd vss vss vss vss vss vss vss vdd vcc m25_ txd1 4 m25_ txd1 5 m25_ rxd1 5 m25_ rxer m25_ col v lb_a dsc_ lb_o e_ lb_w e_ lb_d 29 lb_d 28 vdd vss vss vss vss vss vss vss vdd m25_ txd1 2 m25_ txd1 3 m25_ rxd1 2 m25_ rxd1 3 m25_ rxd1 4 w lb_d 15 lb_a 3 lb_a 4 lb_d 27 lb_d 26 m25_ txd1 0 m25_ txd1 1 m25_ rxd9 m25_ rxd1 0 m25_ rxd1 1 y lb_d 14 lb_d 13 lb_d 12 lb_d 25 lb_d 24 vdd vdd vdd vdd m25_ rxd6 m25_ txd8 m25_ txd9 m25_ rxd7 m25_ rxd8 a a lb_d 11 lb_d 10 lb_d 9 lb_d 23 lb_d 22 m25_ txd6 m25_ txd7 m25_ rxd3 m25_ rxd4 m25_ rxd5 a b lb_d 8 lb_d 7 lb_d 6 lb_d 21 lb_d 20 m25_ txd4 m25_ txd5 m25_ rxd0 m25_ rxd1 m25_ rxd2 a c lb_d 5 lb_d 4 lb_d 3 lb_d 19 lb_d 18 m25_ txd2 m25_ txd3 m23_ crs m23_ rxd0 m23_ rxd1 a d lb_d 2 lb_d 1 lb_d 0 lb_d 17 lb_d 16 vcc vcc vcc vcc vcc m25_ txd0 m25_ txd1 m23_ txd1 m23_ txd0 m23_ txen a e m0_t xen m0_t xd0 m0_t xd1 m3_t xd1 m3_t xen m3_r xd0 m5_t xd1 m5_t xen m5_r xd0 m8_t xd1 m8_t xen m8_r xd0 m10_ txd1 m10_ txen m10_ rxd0 m13_ txd1 m16_ txd0 m15_ txd1 m16_ rxd1 m15_ txen m15_ rxd0 m18_ txd1 m18_ txen m18_ rxd0 m20_ txd1 m20_ txen m20_ rxd0 m22_ rxd1 af m0_r xd1 m0_r xd0 m0_c rs m3_t xd0 m3_c rs m3_r xd1 m5_t xd0 m5_c rs m5_r xd1 m8_t xd0 m8_c rs m8_r xd1 m10_ txd0 m10_ crs m10_ rxd1 m13_ txd0 m13_ crs m13_ rxd1 m14_ crs m16r xd0 m15_ rxd1 m17_ rxd0 m17_ crs m18_ rxd1 m20_ txd0 m20_ crs m20_ rxd1 m22_ rxd0 m22_ crs a g m1_t xen m1_t xd0 m1_t xd1 m2_t xd1 m2_c rs m4_t xd1 m4_c rs m6_t xd1 m6_c rs m7_t xd1 m7_c rs m9_t xd1 m9_c rs m11_ txd1 m11_ crs m12_ txd1 m12_ crs m14_ txd1 m15_ txd0 m16_ txd1 m16_ crs m18_ txd0 m18_ crs m19_ txd1 m19_ crs m21_ txd1 m21_ crs m22_ txen m22_ txd0 a h m1_r xd0 m1_c rs m2_t xd0 m2_r xd0 m4_t xd0 m4_r xd0 m6_t xd0 m6_r xd0 m7_t xd0 m7_r xd0 m9_t xd0 m9_r xd0 m11_ txd0 m11_ rxd0 m12_ txd0 m12_ rxd0 m14_ txd0 m14_ rxd0 m13_ rxd0 m15_ crs m17_ txd0 m17_ rxd1 m19_ txd0 m19_ rxd0 m21_ txd0 m21_ rxd0 m22_ txd1 aj m1_r xd1 m2_t xen m2_r xd1 m4_t xen m4_r xd1 m6_t xen m6_r xd1 m7_t xen m7_r xd1 m9_t xen m9_r xd1 m11_ txen m11_ rxd1 m12_ txen m12_ rxd1 m14_ txen m14_ rxd1 m16_ txen m13_ txen m17_ txen m17_ txd1 m19_ txen m19_ rxd1 m21_ txen m21_ rxd1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
MVTX2603 data sheet 78 zarlink semiconductor inc. 14.2 ball ? signal descriptions all pins are cmos type; all input pins are 5 volt tolerance; and all output pins are 3.3 cmos drive. 14.2.1 ball signal descriptions ball signal descriptions table ball no(s) symbol i/o description i 2 c interface note: use i 2 c and serial control interface to configure the system a24 scl output i 2 c data clock a25 sda i/o-ts with pull up i 2 c data i/o serial control interface a26 strobe input with weak internal pull up serial strobe pin b26 d0 input serial data input c25 autofd output with pull up serial data output (autofd) frame buffer interface d20, b21, d19, e19,d18, e18, d17, e17, d16, e16, d15, e15, d14, e14, d13, e13, d21, e21, a18, b18, c18, a17, b17, c17, a16, b16, c16, a15, b15, c15, a14, b14, d9, e9, d8, e8, d7, e7, d6, e6, d5, e5, d4, e4, d3, e3, d2, e2, a7, b7, a6, b6, c6, a5, b5, c5, a4, b4, c4, a3, b3, c3, b2, c2 la_d[63:0] i/o-ts with pull up frame bank a? data bit [63:0] c14, a13, b13, c13, a12, b12, c12, a11, b11, c11, d11, e11, a10, b10, d10, e10, a8, c7 la_a[20:3] output frame bank a ? address bit [20:3] b8 la_adsc# output with pull up frame bank a address status control c1 la_clk output frame bank a clock input c9 la_we# output with pull up frame bank a write chip select for one layer sram application d12 la_we0# output with pull up frame bank a write chip select for lower layer of two layers sram application e12 la_we1# output with pull up frame bank a write chip select for upper layer of two layers sram application
MVTX2603 data sheet 79 zarlink semiconductor inc. c8 la_oe# output with pull up frame bank a read chip select for one layer sram application a9 la_oe0# output with pull up frame bank a read chip select for lower layer of two layers sram application b9 la_oe1# output with pull up frame bank a read chip select for upper layer of two layers sram application f4, f5, g4, g5, h4, h5, j4, j5, k4, k5, l4, l5, m4, m5, n4, n5, g3, h1, h2, h3, j1, j2, j3, k1, k2, k3, l1, l2, l3, m1, m2, m3, u4, u5, v4, v5, w4, w5, y4, y5, aa4, aa5, ab4, ab5, ac4, ac5, ad4, ad5, w1, y1, y2, y3, aa1, aa2, aa3, ab1, ab2, ab3, ac1, ac2, ac3, ad1, ad2, ad3 lb_d[63:0] i/o-ts with pull up. fr ame bank b? data bit [63:0] n3, n2, n1, p3, p2, p1, r5, r4, r3, r2, r1, t5, t4, t3, t2, t1, w3, w2 lb_a[20:3] output frame bank b ? address bit [20:3] v1 lb_adsc# output with pull up frame bank b address status control g1 lb_clk output frame bank b clock input v3 lb_we# output with pull up frame bank b write chip select for one layer sram application p4 lb_we0# output with pull up frame bank b write chip select for lower layer of two layers sram application p5 lb_we1# output with pull up frame bank b write chip select for upper layer of two layers sram application v2 lb_oe# output with pull up frame bank b read chip select for one layer sram application u1 lb_oe0# output with pull up frame bank b write chip select for lower layer of two layers sram application u2 lb_oe1# output with pull up frame bank b write chip select for upper layer of two layers sram application fast ethernet access ports [23:0] rmii r28 m_mdc output mii management data clock ? (common for all mii ports [23:0]) ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 80 zarlink semiconductor inc. p28 m_mdio i/o-ts with pull up mii management data i/o ? (common for all mii ports ?[23:0])) r29 m_clki input reference input clock ac29, ae28, aj27, af27, aj25, af24, ah23, ae19, af21, aj19, af18, aj17, aj15, af15, aj13, af12, aj11, aj9, af9, aj7, af6, aj5, aj3, af1 m[23:0]_rxd[1] input with weak internal pull up resistors. ports [23:0] ? receive data bit [1] ac28, af28, ah27, ae27, ah25, ae24, af22, af20, ae21, ah19, ah20, ah17, ah15, ae15, ah13, ae12, ah11, ah9, ae9, ah7, ae6, ah5, ah2, af2 m[23:0]_rxd[0] input with weak internal pull up resistors ports [23:0] ? receive data bit [0] ac27, af29, ag27, af26, ag25, ag23, af23, ag21, ah21, af19, af17, ag17, ag15, af14, ag13, af11, ag11, ag9, af8, ag7, af5, ag5, ah3, af3 m[23:0]_crs_dv input wi th weak internal pull down resistors. ports [23:0] ? carrier sense and receive data valid ad29, ag28, aj26, ae26, aj24, ae23, aj22, aj20, ae20, aj18, aj21, aj16, aj14, ae14, aj12, ae11, aj10, aj8, ae8, aj6, ae5, aj4, ag1, ae1 m[23:0]_txen i/o- ts with pull up, slew ports [23:0] ? transmit enable strap option for rmii/gpsi ad27, ah28, ag26, ae25, ag24, ae22, aj23, ag20, ae18, ag18, ae16, ag16, ag14, ae13, ag12, ae10, ag10, ag8, ae7, ag6, ae4, ag4, ag3, ae3 m[23:0]_txd[1] output, slew ports [ 23:0] ? transmit data bit [1] ad28, ag29, ah26, af25, ah24, ag22, ah22, ae17, ag19, ah18, af16, ah16, ah14, af13, ah12, af10, ah10, ah8, af7, ah6, af4, ah4, ag2, ae2 m[23:0]_txd[0] output, slew ports [ 23:0] ? transmit data bit [0] gmii/tbi gigabit ethernet access ports 0 & 1 u26, u25, v26, v25, w26, w25, y27, y26, aa26, aa25, ab26, ab25, ac26, ac25, ad26, ad25 m25_txd[15:0] output transmit data bit [15:0] [7:0] - gmii [9:0] - tbi [15:0] - 2g ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 81 zarlink semiconductor inc. t28 m25_rx_dv input w/ pull down receive data valid u28 m25_rx_er input w/ pull up receive error r25 m25_crs input w/ pull down carrier sense u29 m25_col input w/ pull up collision detected t29 m25_rxclk input w/ pull up receive clock u27, v29, v28, v27, w29, w28, w27, y29, y28, y25, aa29, aa28, aa27, ab29, ab28, ab27 m25_rxd[15:0] input w/ pull up receive data bit [15:0] [7:0] - gmii [9:0] - tbi [15:0] - 2g t26 m25_tx_en output w/ pull up transmit data enable r26 m25_tx_er output w/ pull up transmit error t27 m25_mtxclk input w/ pull down mii mode transmit clock t25 m25_ txclk output gigabit transmit clock p29 gref_clk0 input w/ pull up gigabit reference clock g26, g25, h26, h25, j26, j25, k25, k26, m25, l26, m26, l25, n26, n25, p26, p25 m26_txd[15:0] output transmit data bit [15:0] [7:0] - gmii [9:0] - tbi [15:0] - 2 g f28 m26_rx_dv input w/ pull down receive data valid g28 m26_rx_er input w/ pull up receive error e25 m26_crs input w/ pull down carrier sense g29 m26_col input w/ pull up collision detected f29 m26_rxclk input w/ pull up receive clock g27,h29, h28, h27, j29, j28, j27, k29, k28, k27, l29, l28, l27, m29, m28, m27 m26_rxd[15:0] input w/ pull up receive data bit [15:0] [7:0] - gmii [9:0] - tbi [15:0] - 2 g f26 m26_tx_en output w/ pull up transmit data enable e26 m26_tx_er output w/ pull up transmit error f27 m26_mtxclk input w/ pull down m ii mode transmit clock f25 m26_ txclk output gigabit transmit clock n29 gref_clk1 input w/ pull up gigabit reference clock ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 82 zarlink semiconductor inc. led interface c29 led_clk/tstout0 i/o- ts with pull up led serial interface output clock d29 led_syn/tstout1 i/o- ts with pull up led output data stream envelope e29 led_bit/tstout2 i/o- ts with pull up led serial data output stream b28 g1_rxtx#/tstout 3 i/o- ts with pull up led for gigabit port 1 (receive + transmit) c28 g1_dpcol#/tstou t4 i/o- ts with pull up led for gigabit port 1 (full duplex + collision) d28 g1_link#/tstout5 i/o- ts with pull up led for gigabit port 1 e28 g2_rxtx#/tstout 6 i/o- ts with pull up led for gigabit port 2 (receive + transmit) a27 g2_dpcol#/tstou t7 i/o- ts with pull up led for gigabit port 2 (full duplex + collision) b27 g2_link#/tstout8 i/o- ts with pull up led for gigabit port 2 c27 init_done/tstout 9 i/o- ts with pull up system start operation d27 init_start/tstou t10 i/o- ts with pull up start initialization c26 checksum_ok/ts tout11 i/o- ts with pull up eeprom read ok d26 fcb_err/tstout1 2 i/o- ts with pull up fcb memory self test fail d25 mct_err/tstout1 3 i/o- ts with pull up mct memory self test fail d24 bist_in_prc/tsto ut14 i/o- ts with pull up processing memory self test e24 bist_done/tstou t15 i/o- ts with pull up memory self test done trunk enable c22 trunk0 input w/ weak internal pull down resistors trunk port enable a21 trunk1 input w/ weak internal pull down resistors trunk port enable b24 trunk2 input w/ weak internal pull down resistors trunk port enable test facility ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 83 zarlink semiconductor inc. u3 t_mode0 i/o-ts test pin ? set mode upon reset, and provides nand tree test output during test mode (pull up) c10 t_mode1 i/o-ts test pin ? set mode upon reset, and provides nand tree test output during test mode (pull up) t_mode1 t_mode0 0 0 nandtree 0 1 reserved 1 0 reserved 1 1 regular operation t_mode0 and t_mode1 are used for manufacturing tests. the signals should both be set to 1 for regular operation. f3 scan_en input with pull down scan enable 0 - normal mode (unconnected) e27 scanmode input with pull dow n 1 - enables test mode. 0 - normal mode (unconnected) system clock, power, and ground pins e1 sclk input system clock at 100 mhz k12, k13, k17,k18 m10, n10, m20, n20, u10, v10, u20, v20, y12, y13, y17, y18 vdd power +2.5 volt dc supply f13, f14, f15, f16, f17, n6, p6, r6, t6, u6, n24, p24, r24, t24, u24, ad13, ad14, ad15, ad16, ad17 vcc power +3.3 volt dc supply m12, m13, m14, m15, m16, m17, m18, n12, n13, n14, n15, n16, n17, n18, p12, p13, p14, p15, p16, p17, p18, r12, r13, r14, r15, r16, r17, r18, t12, t13, t14, t15, t16, t17, t18, u12, u13, u14, u15, u16, u17, u18, v12, v13, v14, v15, v16, v17, v18, vss power ground ground f1 avcc analog power analog +2.5 volt dc supply d1 agnd analog ground analog ground ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 84 zarlink semiconductor inc. misc d22 scancol input scans the collision signal of home phy d23 scanclk input/ output clock for scanning home phy collision and link e23 scanlink input link up signal from home phy f2 resin# input reset input g2 resetout# output reset phy e20, b25 reserved i/o-ts reserved pins. leave unconnected. bootstrap pins (default= pull up, 1= pull up 0= pull down) after reset tstout0 to tstout15 are used by the led interface. c29 tstout0 default: active high (1) giga link polarity 0 - active low 1 - active high d29 tstout1 default: enable (1) rmii mac power saving enable 0 - no power saving 1 - power saving e29 tstout2 default: enable (1) recommend disable (0) with pull-down giga half duplex support 0 - disable 1 - enable c28, b28 tstout[4:3] reserved c28 tstout4 default: sbram (1) memory is sbram/zbt 0 - zbt 1 ? pipeline sbram d28 tstout5 default: sclk (1) scan speed 0 - ? sclk(hpna) 1 - sclk e28 tstout6 reserved a27 tstout7 default: 128 k x 32 or 128 k x 64 (1) memory size 0 - 256 k x 32 or 256 k x 64 (4 m total) 1 - 128 k x 32 or 128 k x 64 (2 m total) ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 85 zarlink semiconductor inc. b27 tstout8 default: not installed (1) eeprom installed 0 - eeprom installed 1 - eeprom not installed c27 tstout9 default: mct aging enable (1) mct aging 0 - mct aging disable 1 - mct aging enable d27 tstout10 default: fcb aging enable (1) fcb aging 0 - fcb aging disable 1 - fcb aging enable c26 tstout11 default: timeout reset enable (1) timeout reset 0 - time out reset disable 1 - time out reset enable. issue reset if any state machine did not go back to idle for 5 sec. d26 tstout12 default: normal (1) test speed up 0 - enable test speed up. do not use. 1 - disable test speed up d25 tstout13 default: single depth (1) fdb ram depth (1 or 2 layers) 0 - two layers 1 - one layer d24 tstout14 reserved. e24 tstout15 default: normal operation sram test mode 0 - enable test mode 1 - normal operation t26, r26 g0_txen, g0_txer default: pcs giga0 mode: g0_txen g0_txer 0 0 mii 0 1 2 g 1 0 gmii 1 1 pcs f26, e26 g1_txen, g1_txer default: pcs giga1 mode: g1_txen g1_txer 0 0 mii 0 1 2 g 1 0 gmii 1 1 pcs ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 86 zarlink semiconductor inc. note: # = active low signal input = input signal in-st = input signal with schmitt-trigger output = output signal (tri-state driver) out-od = output signal with open-drain driver i/o-ts = input & output signal with tri-state driver i/o-od = input & output signal with open-drain driver 14.3 ball ? signal name ad29, ag28, aj26, ae26, aj24, ae23, aj22, aj20, ae20, aj18, aj21, aj16, aj14, ae14, aj12, ae11, aj10, aj8, ae8, aj6, ae5, aj4, ag1, ae1, m[23:0]_txen default: rmii 0 ? gpsi 1 - rmii c21 p_d must be pulled-down reserved. must be pulled-down. c19, b19, a19 oe_clk[2:0] default: 111 programmable delay for internal oe_clk from sclk input. the oe_clk is used for generating the oe0 and oe1 signals suggested value is 001. c20, b20, a20 la_clk[2:0] default: 111 program mable delay for la_clk and lb_clk from internal oe_clk. the la_clk and lb_clk delay from sclk is the sum of the delay programmed in here and the delay in p_d[15:13]. suggested value is 011. b22, a22, c23, b23, a23, c24 mirror[5:0] default: 111111 dedicated port mirror m ode. the first 5 bits select the port to be mirrored. the last bit selects either ingress or egress data. ball ? signal name table ball no. signal name ball no. signal name ball no. signal name d20 la_d[63] d3 la_d[19] a9 la_oe0# b21 la_d[62] e3 la_d[18] b9 la_oe1# d19 la_d[61] d2 la_d[17] f4 lb_d[63] e19 la_d[60] e2 la_d[16] f5 lb_d[62] d18 la_d[59] a7 la_d[15] g4 lb_d[61] e18 la_d[58] b7 la_d[14] g5 lb_d[60] ball signal descriptions table (continued) ball no(s) symbol i/o description
MVTX2603 data sheet 87 zarlink semiconductor inc. d17 la_d[57] a6 la_d[13] h4 lb_d[59] e17 la_d[56] b6 la_d[12] h5 lb_d[58] d16 la_d[55] c6 la_d[11] j4 lb_d[57] e16 la_d[54] a5 la_d[10] j5 lb_d[56] d15 la_d[53] b5 la_d[9] k4 lb_d[55] e15 la_d[52] c5 la_d[8] k5 lb_d[54] d14 la_d[51] a4 la_d[7] l4 lb_d[53] e14 la_d[50] b4 la_d[6] l5 lb_d[52] d13 la_d[49] c4 la_d[5] m4 lb_d[51] e13 la_d[48] a3 la_d[4] m5 lb_d[50] d21 la_d[47] b3 la_d[3] n4 lb_d[49] e21 la_d[46] c3 la_d[2] n5 lb_d[48] a18 la_d[45] b2 la_d[1] g3 lb_d[47] b18 la_d[44] c2 la_d[0] h1 lb_d[46] c18 la_d[43] c14 la_a[20] h2 lb_d[45] a17 la_d[42] a13 la_a[19] h3 lb_d[44] b17 la_d[41] b13 la_a[18] j1 lb_d[43] c17 la_d[40] c13 la_a[17] j2 lb_d[42] a16 la_d[39] a12 la_a[16] j3 lb_d[41] b16 la_d[38] b12 la_a[15] k1 lb_d[40] c16 la_d[37] c12 la_a[14] k2 lb_d[39] a15 la_d[36] a11 la_a[13] k3 lb_d[38] b15 la_d[35] b11 la_a[12] l1 lb_d[37] c15 la_d[34] c11 la_a[11] l2 lb_d[36] a14 la_d[33] d11 la_a[10] l3 lb_d[35] b14 la_d[32] e11 la_a[9] m1 lb_d[34] d9 la_d[31] a10 la_a[8] m2 lb_d[33] e9 la_d[30] b10 la_a[7] m3 lb_d[32] d8 la_d[29] d10 la_a[6] u4 lb_d[31] e8 la_d[28] e10 la_a[5] u5 lb_d[30] ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 88 zarlink semiconductor inc. d7 la_d[27] a8 la_a[4] v4 lb_d[29] e7 la_d[26] c7 la_a[3] v5 lb_d[28] d6 la_d[25] b8 la_adsc# w4 lb_d[27] e6 la_d[24] c1 la_clk w5 lb_d[26] d5 la_d[23] c9 la_we# y4 lb_d[25] e5 la_d[22] d12 la_we0# y5 lb_d[24] d4 la_d[21] e12 la_we1# aa4 lb_d[23] e4 la_d[20] c8 la_oe# aa5 lb_d[22] ab4 lb_d[21] u2 lb_oe1# ah7 m[4]_rxd[0] ab5 lb_d[20] r28 mdc ae6 m[3]_rxd[0] ac4 lb_d[19] p28 mdio ah5 m[2]_rxd[0] ac5 lb_d[18] r29 m_clk ah2 m[1]_rxd[0] ad4 lb_d[17] ac29 m[23]_rxd [1] af2 m[0]_rxd[0] ad5 lb_d[16] ae28 m[22]_rxd[1] ac27 m[23]_crs_dv w1 lb_d[15] aj27 m[21]_rxd[1] af29 m[22]_crs_dv y1 lb_d[14] af27 m[20]_rxd[1] ag27 m[21]_crs_dv y2 lb_d[13] aj25 m[19]_rxd[1] af26 m[20]_crs_dv y3 lb_d[12] af24 m[18]_rxd[1] ag25 m[19]_crs_dv aa1 lb_d[11] ah23 m[17]_rxd[1] ag23 m[18]_crs_dv aa2 lb_d[10] ae19 m[16]_rxd[1] af23 m[17]_crs_dv aa3 lb_d[9] af21 m[15]_rxd[1] ag21 m[16]_crs_dv ab1 lb_d[8] aj19 m[14]_rxd[1] ah21 m[15]_crs_dv ab2 lb_d[7] af18 m[13]_rxd[1] af19 m[14]_crs_dv ab3 lb_d[6] aj17 m[12]_rxd[1] af17 m[13]_crs_dv ac1 lb_d[5] aj15 m[11]_rxd[1] ag17 m[12]_crs_dv ac2 lb_d[4] af15 m[10]_rxd[1] ag15 m[11]_crs_dv ac3 lb_d[3] aj13 m[9]_rxd[1] af14 m[10]_crs_dv ad1 lb_d[2] af12 m[8]_rxd[1] ag13 m[9]_crs_dv ad2 lb_d[1] aj11 m[7]_rxd[1] af11 m[8]_crs_dv ad3 lb_d[0] aj9 m[6]_rxd[1] ag11 m[7]_crs_dv ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 89 zarlink semiconductor inc. n3 lb_a[20] af9 m[5]_rxd[1] ag9 m[6]_crs_dv n2 lb_a[19] aj7 m[4]_rxd[1] af8 m[5]_crs_dv n1 lb_a[18] af6 m[3]_rxd[1] ag7 m[4]_crs_dv p3 lb_a[17] aj5 m[2]_rxd[1] af5 m[3]_crs_dv p2 lb_a[16] aj3 m[1]_rxd[1] ag5 m[2]_crs_dv p1 lb_a[15] af1 m[0]_rxd[1] ah3 m[1]_crs_dv r5 lb_a[14] ac28 m[23]_rxd[0] af3 m[0]_crs_dv r4 lb_a[13] af28 m[22]_rxd[0] ad29 m[23]_txen r3 lb_a[12] ah27 m[21]_rxd[0] ag28 m[22]_txen r2 lb_a[11] ae27 m[20]_rxd[0] aj26 m[21]_txen r1 lb_a[10] ah25 m[19]_rxd[0] ae26 m[20]_txen t5 lb_a[9] ae24 m[18]_rxd[0] aj24 m[19]_txen t4 lb_a[8] af22 m[17]_rxd[0] ae23 m[18]_txen t3 lb_a[7] af20 m[16]_rxd[0] aj22 m[17]_txen t2 lb_a[6] ae21 m[15]_rxd[0] aj20 m[16]_txen t1 lb_a[5] ah19 m[14]_rxd[0] ae20 m[15]_txen w3 lb_a[4] ah20 m[13]_rxd[0] aj18 m[14]_txen w2 lb_a[3] ah17 m[12]_rxd[0] aj21 m[13]_txen v1 lb_adsc# ah15 m[11]_rxd[0] aj16 m[12]_txen g1 lb_clk ae15 m[10]_rxd[0] aj14 m[11]_txen v3 lb_we# ah13 m[9]_rxd[0] ae14 m[10]_txen p4 lb_we0# ae12 m[8]_rxd[0] aj12 m[9]_txen p5 lb_we1# ah11 m[7]_rxd[0] ae11 m[8]_txen v2 lb_oe# ah9 m[6]_rxd[0] aj10 m[7]_txen u1 lb_oe0# ae9 m[5]_rxd[0] aj8 m[6]_txen ae8 m[5]_txen ah8 m[6]_txd[0] g27 m26_rxd[15] aj6 m[4]_txen af7 m[5]_txd[0] h29 m26_rxd[14] ae5 m[3]_txen ah6 m[4]_txd[0] h28 m26_rxd[13] aj4 m[2]_txen af4 m[3]_txd[0] h27 m26_rxd[12] ag1 m[1]_txen ah4 m[2]_txd[0] j29 m26_rxd[11] ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 90 zarlink semiconductor inc. ae1 m[0]_txen ag2 m[1]_txd[0] j28 m26_rxd[10] ad27 m[23]_txd[1] ae2 m[0]_txd[0] j27 m26_rxd[9] ah28 m[22]_txd[1] u26 m25_txd[15] k29 m26_rxd[8] ag26 m[21]_txd[1] u25 m25_txd[14] k28 m26_rxd[7] ae25 m[20]_txd[1] v26 m25_txd[13] k27 m26_rxd[6] ag24 m[19]_txd[1] v25 m25_t xd[12] l29 m26_rxd[5] ae22 m[18]_txd[1] w26 m25_txd[11] l28 m26_rxd[4] aj23 m[17]_txd[1] w25 m25_t xd[10] l27 m26_rxd[3] ag20 m[16]_txd[1] y27 m25_txd[9] m29 m26_rxd[2] ae18 m[15]_txd[1] y26 m25_txd[8] m28 m26_rxd[1] ag18 m[14]_txd[1] aa26 m25_txd[7] m27 m26_rxd[0] ae16 m[13]_txd[1] aa25 m25_txd[6] g26 m26_txd[15] ag16 m[12]_txd[1] ab26 m25_txd[5] g25 m26_txd[14] ag14 m[11]_txd[1] ab25 m25_txd[4] h26 m26_txd[13] ae13 m[10]_txd[1] ac26 m25_t xd[3] h25 m26_txd[12] ag12 m[9]_txd[1] ac25 m25_txd[2] j26 m26_txd[11] ae10 m[8]_txd[1] ad26 m25_t xd[1] j25 m26_txd[10] ag10 m[7]_txd[1] ad25 m25_txd[0] k25 m26_txd[9] ag8 m[6]_txd[1] u27 m25_rxd[15] k26 m26_txd[8] ae7 m[5]_txd[1] v29 m25_rxd[14] m25 m26_txd[7] ag6 m[4]_txd[1] v28 m25_r xd[13] l26 m26_txd[6] ae4 m[3]_txd[1] v27 m25_rxd[12] m26 m26_txd[5] ag4 m[2]_txd[1] w29 m25_rxd[11] l25 m26_txd[4] ag3 m[1]_txd[1] w28 m25_rxd[10] n26 m26_txd[3] ae3 m[0]_txd[1] w27 m25_rxd[9] n25 m26_txd[2] ad28 m[23]_txd[0] y29 m25_rxd[8] p26 m26_txd[1] ag29 m[22]_txd[0] y28 m25_rxd[7] p25 m26_txd[0] ah26 m[21]_txd[0] y25 m25_rxd[6] f28 m26_rx_dv af25 m[20]_txd[0] aa29 m25_rxd[5] g28 m26_rx_er ah24 m[19]_txd[0] aa28 m25_rxd[4] e25 m26_crs ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 91 zarlink semiconductor inc. ag22 m[18]_txd[0] aa27 m25_rxd[3] g29 m26_col ah22 m[17]_txd[0] ab29 m25_rxd[2] f29 m26_rxclk ae17 m[16]_txd[0] ab28 m25_rxd[1] f26 m26_tx_en ag19 m[15]_txd[0] ab27 m25_rxd[0] e26 m26_tx_er ah18 m[14]_txd[0] r26 m25_tx_er f25 m26_txclk af16 m[13]_txd[0] t25 m25_txclk e24 bist_done/tstout[15] ah16 m[12]_txd[0] t26 m25_tx_en d2 4 bist_in_prc/tst0ut[14] ah14 m[11]_txd[0] t28 m25_rx_dv d25 mct_err/tstout[13] af13 m[10]_txd[0] u28 m25_rx_er d26 fcb_err/tstout[12] ah12 m[9]_txd[0] r25 m25_crs c26 c hecksum_ok/tstout[11] af10 m[8]_txd[0] u29 m25_col d27 init_start/tstout[10] ah10 m[7]_txd[0] t29 m25_rxclk c27 init_done/tstout[9] b27 g2_link#/tstout[8] u18 vss n12 vss a27 g2_dpcol#/tstout[7] v12 vss n13 vss e28 g2_rxtx#/tstout[6] v13 vss k17 vdd d28 g1_link#/tstout[5] v14 vss k18 vdd c28 g1_dpcol#/tstout[4] v15 vss m10 vdd b28 g1_rxtx#/tstout[3] v16 vss n10 vdd e29 led_bit/tstout[2] v17 vss m20 vdd d29 led_syn/tstout[1] v18 vss n20 vdd c29 led_clk/tstout[0] n14 vss u10 vdd n29 gref_clk1 n15 vss v10 vdd p29 gref_clk0 n16 vss u20 vdd f3 scan_en n17 vss v20 vdd e1 sclk n18 vss y12 vdd u3 t_mode0 p12 vss y13 vdd c10 t_mode1 p13 vss y17 vdd b24 trunk2 p14 vss y18 vdd a21 trunk1 p15 vss k12 vdd c22 trunk0 p16 vss k13 vdd ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 92 zarlink semiconductor inc. a26 strobe c19 oe_clk2 m16 vss b26 d0 b19 oe_clk1 m17 vss c25 autofd a19 oe_clk0 m18 vss a24 scl r13 vss f16 vcc a25 sda r14 vss f17 vcc f1 avcc r15 vss n6 vcc d1 agnd r16 vss p6 vcc d22 scancol r17 vss r6 vcc e23 scanlink r18 vss t6 vcc e27 scanmode t12 vss u6 vcc n28 t13 vss n24 vcc n27 t14 vss p24 vcc f2 resin# t15 vss r24 vcc g2 resetout# t16 vss t24 vcc b22 mirror5 t17 vss u24 vcc a22 mirror4 t18 vss ad13 vcc c23 mirror3 u12 vss ad14 vcc b23 mirror2 u13 vss ad15 vcc a23 mirror1 u14 vss ad16 vcc c24 mirror0 u15 vss ad17 vcc d23 scanclk u16 vss f13 vcc t27 m25_mtxclk u17 vss f14 vcc f27 m26_mtxclk m12 vss f15 vcc c20 la_clk2 m13 vss r12 vss b20 la_clk1 m14 vss b25 reserved a20 la_clk0 m15 vss e20 reserved c21 p_d p17 vss p18 vss ball ? signal name table (continued) ball no. signal name ball no. signal name ball no. signal name
MVTX2603 data sheet 93 zarlink semiconductor inc. 14.4 ac/dc timing 14.4.1 absolute maximum ratings storage temperature -65 c to +150 c operating temperature -40 c to +85 c maximum junction temperature +125 c supply voltage vcc with respect to v ss +3.0 v to +3.6 v supply voltage vdd with respect to v ss +2.38 v to +2.75 v voltage on input pins -0.5 v to (vcc + 0.3 v) caution: stress above those listed may damage the device. exposure to the absolute maximum ratings for extended periods may affect device reliability. functi onality at or above these limits is not implied. 14.4.2 dc electrical characteristics vcc = 3.0 v to 3.6 v (3.3v +/- 10%)t ambient = -40 c to +85 c vdd = 2.5 v +10% - 5% 14.4.3 recommended operating conditions symbol parameter description min. typ. max. unit f osc frequency of operation 100 mhz i cc supply current ? @ 100 mhz (vcc =3.3 v) 450 ma i dd supply current ? @ 100 mhz (vdd =2.5 v) 1500 ma v oh output high voltage (cmos) 2.4 v v ol output low voltage (cmos) 0.4 v v ih-ttl input high voltage (ttl 5 v tolerant) 2.0 vcc + 2.0 v v il-ttl input low voltage (ttl 5 v tolerant) 0.8 v i il input leakage current (0.1 v < v in < vcc) (all pins except those with internal pull-up/pull-down resistors) 10 a i ol output leakage current (0.1 v < vout < vcc) 10 a c in input capacitance 5 pf c out output capacitance 5 pf c i/o i/o capacitance 7 pf ja thermal resistance with 0 air flow 11.2 c/w ja thermal resistance with 1 m/s air flow 10.2 c/w ja thermal resistance with 2 m/s air flow 8.9 c/w jc thermal resistance between junction and case 3.1 c/w jb thermal resistance between junction and board 6.6 c/w
MVTX2603 data sheet 94 zarlink semiconductor inc. 14.4.4 typical reset & bootstrap timing diagram figure 18 - typical reset & bootstrap timing diagram symbol parameter min. typ. note: r1 delay until resetout# is tri-stated 10 ns resetout# state is then determined by the external pull-up/down resistor r2 bootstrap stabilization 1 s10 s bootstrap pins sampled on rising edge of resin# a a. the tstout[8:0] pins will switch over to the led interf ace functionality in 3 sclk cycles after resin# goes high r3 resetout# assertion 2 ms table 13 - reset & bootstrap timing resetout# tri-stated resin# r1 r2 r3 bootstrap pins inputs outputs outputs
MVTX2603 data sheet 95 zarlink semiconductor inc. 14.5 local frame buff er sbram memory interface 14.5.1 local sbram memory interface figure 19 - local memory interface ? input setup and hold timing figure 20 - local memory interface - output valid delay timing l1 l2 la_clk la_d[63:0] l3-min l3-max l4-min l4-max l6-min l6-max l7-min l7-max l8-min l8-max la_clk la_d[63:0] la_a[20:3] la_adsc# la_we[1:0]# #### la_oe[1:0]# l9-min l9-max la_we# l10-min l10-max la_oe#
MVTX2603 data sheet 96 zarlink semiconductor inc. symbol parameter -100 mhz min. (ns) max. (ns) note l1 la_d[63:0] input set-up time 4 l2 la_d[63:0] input hold time 1.5 l3 la_d[63:0] output valid delay 1.5 7 c l = 25 pf l4 la_a[20:3] output valid delay 2 7 c l = 30 pf l6 la_adsc# output valid delay 1 7 c l = 30 pf l7 la_we[1:0]#output valid delay 1 7 c l = 25 pf l8 la_oe[1:0]# output valid delay -1 1 c l = 25 pf l9 la_we# output valid delay 1 7 c l = 25 pf l10 la_oe# output valid delay 1 5 c l = 25 pf table 14 - ac characteristics ? local frame buffer sbram memory interface
MVTX2603 data sheet 97 zarlink semiconductor inc. 14.6 local switch database sbram memory interface 14.6.1 local sbram memory interface figure 21 - local memory interface ? input setup and hold timing figure 22 - local memory interface - output valid delay timing l1 l2 lb_clk lb_d[63:0] l3-min l3-max l4-min l4-max l6-min l6-max l8-min l8-max l9-min l9-max l10-min l10-max lb_clk lb_d[31:0] lb_a[21:2] lb_adsc# lb_we[1:0]# lb_oe[1:0]# lb_we# l11-min l11-max lb_oe#
MVTX2603 data sheet 98 zarlink semiconductor inc. symbol parameter -100 mhz min. (ns) max. (ns) note l1 lb_d[63:0] input set-up time 4 l2 lb_d[63:0] input hold time 1.5 l3 lb_d[63:0] output valid delay 1.5 7 c l = 25 pf l4 lb_a[20:3] output valid delay 2 7 c l = 30 pf l6 lb_adsc# output valid delay 1 7 c l = 30 pf l8 lb_we[1:0]#output valid delay 1 7 c l = 25 pf l9 lb_oe[1:0]# output valid delay -1 1 c l = 25 pf l10 lb_we# output valid delay 1 7 c l = 25 pf l11 lb_oe# output valid delay 1 5 c l = 25 pf table 15 - ac characteristics ? local switch database sbram memory interface
MVTX2603 data sheet 99 zarlink semiconductor inc. 14.7 ac characteristics 14.7.1 reduced media independent interface figure 23 - ac characteristics ? reduced media independent interface figure 24 - ac characteristics ? reduced media independent interface symbol parameter -50 mhz note min. (ns) max. (ns) m2 m[23:0]_rxd[1:0] input setup time 4 m3 m[23:0]_rxd[1:0] input hold time 1 m4 m[23:0]_crs_dv input setup time 4 m5 m[23:0]_crs_dv input hold time 1 m6 m[23:0]_txen output delay time 2 11 c l = 20 pf m7 m[23:0]_txd[1:0] output delay time 2 11 c l = 20 pf table 16 - ac characteristics ? reduced media independent interface m6-min m6-max m7-min m7-max m_clki m[23:0]_txen m[23:0] _txd[1:0] m2 m_clki m[23:0]_rxd m[23:0]_crs_dv m3 m4 m5
MVTX2603 data sheet 100 zarlink semiconductor inc. 14.7.2 gigabit media independent interface - port a figure 25 - ac characteristics- gmii figure 26 - ac characteristics ? gigabit media independent interface symbol parameter -125 mhz note min. (ns) max. (ns) g1 m[25]_rxd[15:0] input setup times 2 g2 m[25]_rxd[15:0] input hold times 1 g3 m[25]_rx_dv input setup times 2 g4 m[25]_rx_dv input hold times 1 g5 m[25]_rx_er input setup times 2 g6 m[25]_rx_er input hold times 1 g7 m[25]_crs input setup times 2 g8 m[25]_crs input hold times 1 table 17 - ac characteristics ? gigabit media independent interface g12-min g12-max g13-min g13-max g14-min g14-max m25_txclk m25_txd [15:0] m25_tx_en] m25_tx_er m25_rxclk g1 g2 m25_rxd[15:0] g3 g4 m25 _ rx _ dv g5 g6 m25_rx_er g7 g8 m25 _ rx _ crs
MVTX2603 data sheet 101 zarlink semiconductor inc. 14.7.3 ten bit interface - port a figure 27 - gigabit tbi interface transmit timing figure 28 - gigabit tbi interface receive timing g12 m[25]_txd[15:0] output delay times 1 6 c l = 20 pf g13 m[25]_tx_en output delay times 1 6.5 c l = 20 pf g14 m[25]_tx_er output delay times 1 6 c l = 20 pf symbol paramete r min. (ns) max. (ns) note t1 m25_txd[9:0] output delay time 1 6 c l = 20 pf table 18 - output delay timing symbol paramete r min. (ns) max. (ns) note t2 m25_rxd[9:0] input setup time 3 t3 m25_rxd[9:0] input hold time 3 table 19 - input setup timing symbol parameter -125 mhz note min. (ns) max. (ns) table 17 - ac characteristics ? gigabit media independent interface (continued) m25_txclk m25_txd [9:0] timin timax m25_rxcl k m25_col t2 m25_rxd[9:0] t3 t2 t3
MVTX2603 data sheet 102 zarlink semiconductor inc. 14.7.4 gigabit media independent interface - port b figure 29 - ac characteristics- gmii figure 30 - ac characteristics ? gigabit media independent interface symbol parameter -125 mhz note min. (ns) max. (ns) g1 m[26]_rxd[15:0] input setup times 2 g2 m[26]_rxd[15:0] input hold times 1 g3 m[26]_rx_dv input setup times 2 g4 m[26]_rx_dv input hold times 1 g5 m[26]_rx_er input setup times 2 g6 m[26]_rx_er input hold times 1 g7 m[26]_crs input setup times 2 g8 m[26]_crs input hold times 1 table 20 - ac characteristics ? gigabit media independent interface g12-min g12-max g13-min g13-max g14-min g14-max m26_txclk m26_txd [15:0] m26_tx_en] m26_tx_er m26_rxclk g1 g2 m26_rxd[15:0] g3 g4 m26 _ rx _ dv g5 g6 m26_rx_er g7 g8 m26 _ rx _ crs
MVTX2603 data sheet 103 zarlink semiconductor inc. 14.7.5 ten bit interface - port b figure 31 - gigabit tbi interface transmit timing figure 32 - gigabit tbi interface timing g12 m[26]_txd[15:0] output delay times 1 6 c l = 20 pf g13 m[26]_tx_en output delay times 1 6.5 c l = 20 pf g14 m[26]_tx_er output delay times 1 6 c l = 20 pf symbol parameter min. (ns) max. (ns) note t1 m26_txd[9:0] output delay time 1 6 c l = 20 pf table 21 - output delay timing symbol parameter min. (ns) max. (ns) note t2 m26_rxd[9:0] input setup time 3 t3 m26_rxd[9:0] input hold time 3 table 22 - input setup timing symbol parameter -125 mhz note min. (ns) max. (ns) table 20 - ac characteristics ? gigabit media independent interface (continued) m26_txclk m26_txd [9:0] timin timax m26_rxclk m26_col t2 m26_rxd[9:0] t3 t2 t3
MVTX2603 data sheet 104 zarlink semiconductor inc. 14.7.6 led interface figure 33 - ac characteristics ? led interface 14.7.7 scanlink scancol output delay timing figure 34 - scanlink scancol output delay timing figure 35 - scanlink, scancol setup timing symbol parameter variable freq. note min. (ns) max. (ns) le5 led_syn output valid delay -1 7 c l = 30 pf le6 led_bit output valid delay -1 7 c l = 30 pf table 23 - ac characteristics ? led interface le5-min le5-max le6-min le6-max led_clk led_syn led_bit c5-min c5-max c7-min c7-max scanclk scanlink scancol scanclk c1 c2 scanlink c3 c4 scancol
MVTX2603 data sheet 105 zarlink semiconductor inc. 14.7.8 mdio input setup and hold timing figure 36 - mdio input setup and hold timing figure 37 - mdio output delay timing symbol parameter -25 mhz note min. (ns) max. (ns) c1 scanlink input set-up time 20 c2 scanlink input hold time 2 c3 scancol input setup time 20 c4 scancol input hold time 1 c5 scanlink output valid delay 0 10 c l = 30 pf c7 scancol output valid delay 0 10 c l = 30 pf table 24 - scanlink, scancol timing symbol parameter 1mhz note min. (ns) max. (ns) d1 mdio input setup time 10 d2 mdio input hold time 2 d3 mdio output delay time 1 20 c l = 50 pf table 25 - mdio timing mdc d1 d2 mdio d3-min d3-max mdc mdio
MVTX2603 data sheet 106 zarlink semiconductor inc. 14.7.9 i 2 c input setup timing figure 38 - i 2 c input setup timing figure 39 - i 2 c output delay timing symbol parameter 50 khz note min. (ns) max. (ns) s1 sda input setup time 20 s2 sda input hold time 1 s3* sda output delay time 4 usec 6 usec c l = 30 pf * open drain output. low to high transistor is controlled by external pullup resistor. table 26 - i 2 c timing s1 s2 scl sda s3-min s3-max scl sda
MVTX2603 data sheet 107 zarlink semiconductor inc. 14.7.10 serial interface setup timing figure 40 - serial interface setup timing figure 41 - serial interface output delay timing symbol parameter min. (ns) max. (ns) note d1 d0 setup time 20 d2 d0 hold time 3 s d3 autofd output delay time 1 50 c l = 100 pf d4 strobe low time 5 s d5 strobe high time 5 s table 27 - serial interface timing strobe d1 d2 d0 d1 d2 d4 d5 d3-min d3-max strobe autofd
apprd. issue date acn package code previous package codes: conforms to jedec ms - 034 2.20 e e b e1 dimension d d1 a2 a1 a 1.27 553 max 0.70 2.46 1.17 ref 0.50 min 3. seating plane is defined by the spherical crowns of the solder balls. 1. controlling dimensions are in mm 2. dimension "b" is measured at the maximum solder ball diameter 4. n is the number of solder balls 5. not to scale. note: 0.60 0.90 37.30 37.70 34.50 ref 37.30 37.70 34.50 ref e1 d1 d e e b a2 6. substrate thickness is 0.56 mm
www.zarlink.com information relating to products and services furnished herein by zarlink semiconductor inc. or its subsidiaries (collectively ?zarlink?) is believed to be reliable. however, zarlink assumes no liability for errors that may appear in this publication, or for liability otherwise arising from t he application or use of any such information, product or service or for any infringement of patents or other intellectual property rights owned by third parties which may result from such application or use. neither the supply of such information or purchase of product or service conveys any license, either express or implied, u nder patents or other intellectual property rights owned by zarlink or licensed from third parties by zarlink, whatsoever. purchasers of products are also hereby notified that the use of product in certain ways or in combination with zarlink, or non-zarlink furnished goods or services may infringe patents or other intellect ual property rights owned by zarlink. this publication is issued to provide information only and (unless agreed by zarlink in writing) may not be used, applied or re produced for any purpose nor form part of any order or contract nor to be regarded as a representation relating to the products or services concerned. the products, t heir specifications, services and other information appearing in this publication are subject to change by zarlink without notice. no warranty or guarantee express or implied is made regarding the capability, performance or suitability of any product or service. information concerning possible methods of use is provided as a guide only and does not constitute any guarantee that such methods of use will be satisfactory in a specific piece of equipment. it is the user?s responsibility t o fully determine the performance and suitability of any equipment using such information and to ensure that any publication or data used is up to date and has not b een superseded. manufacturing does not necessarily include testing of all functions or parameters. these products are not suitable for use in any medical products whose failure to perform may result in significant injury or death to the user. all products and materials are sold and services provided subject to zarlink?s conditi ons of sale which are available on request. purchase of zarlink?s i 2 c components conveys a licence under the philips i 2 c patent rights to use these components in and i 2 c system, provided that the system conforms to the i 2 c standard specification as defined by philips. zarlink, zl and the zarlink semiconductor logo are trademarks of zarlink semiconductor inc. copyright zarlink semiconductor inc. all rights reserved. technical documentation - not for resale for more information about all zarlink products visit our web site at

▲Up To Search▲

Price & Availability of MVTX2603

	To Download MVTX2603 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .